sACN icon indicating copy to clipboard operation
sACN copied to clipboard

✨ handle resend errors

Open lukas-runge opened this issue 1 year ago • 0 comments

Hi @k-yle,

when using the minRefreshRate feature to resend packets continuously the socket might throw errors. One example would be disconnecting and reconnecting the ethernet connection. In this case the unhandled error would crash the whole application and there would be no way for users of the library to catch those and handle those appropriately. This is why I implemented two events that help users handling those cases:

  1. error: contains the Error object for further handling
  2. changedResendStatus: to gracefully recover from disconnection events without necessarily needing to destroy and recreate the Sender instance.

Best regards, @lukas-runge

lukas-runge avatar Jul 22 '24 19:07 lukas-runge