Is there a way to obtain extra information about the reason of a NetStream.Connect.Closed event? For example, I'd like to be able to tell my users if the other end timed out or was closed by the user.
I've been looking into this, but I have come to the conclusion that it is not possible. If this is correct, where would be the right place to suggest such a feature?
the distinction between a timeout and an active close is not conveyed by the current API.
on the publisher side, you could have a special NetStream.send() method for "i'm actively closing now" that you send right before you close. or you could deduce a timeout by observing an extended period of dry buffer or a persistent lack of heartbeat/watchdog messages preceding a NetStream.Connect.Closed at the subscriber end.
Is there a chance that this information will be available in future versions of the API?
Also, sending a message right before calling close doesn't seem to work, the message never reaches the other side. Is this the expected behaviour?
Thanks for your help!