Open derekcollison opened 4 years ago
We have some errors that are sync in nature, either from the NATS server or from threaded callbacks for message handlers.
Should we have the notion of last_error() for both NATS system and another for the message handlers that would hang off of SubscriptionHandler?
last_error()
This can be closed as err callback was added, agree @derekcollison ?
We have async err AFAIK now, but this might still be useful. WDYT?
We have some errors that are sync in nature, either from the NATS server or from threaded callbacks for message handlers.
Should we have the notion of
last_error()
for both NATS system and another for the message handlers that would hang off of SubscriptionHandler?