Hello again Dmitry,

besides our different views on the use of exceptions, your main issue seems to be that your are not notified of the resubscription failure. If this is the case, I agree this behavior of the library may be improved.

At the moment, the library tries again to resubscribe the tables each time it reconnects. If a resubscription fails, it is simply logged and then retried the next time. The library could instead notify your delegate of the exception (instead of logging it) and give up resubscribing the table.

Let me know if this would be a better behavior for your application.
Best regards,

Gianluca