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:
error: contains the Error object for further handling
changedResendStatus: to gracefully recover from disconnection events without necessarily needing to destroy and recreate the Sender instance.
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:error
: contains theError
object for further handlingchangedResendStatus
: to gracefully recover from disconnection events without necessarily needing to destroy and recreate theSender
instance.Best regards, @lukas-runge