[Red5] Missing notification about closed connection
branko_pecnik at t-2.net
Sat Mar 31 07:08:41 EST 2007
I think this was solved 3.3.2007 (r1747).
Od: Red5-bounces at osflash.org [mailto:Red5-bounces at osflash.org] Namesto
Poslano: 31. marec 2007 0:17
Za: Red5 at osflash.org
Zadeva: [Red5] Missing notification about closed connection
We are trying to build some 1:1 video chat application. Therefore we
open one NetConnection from user A to the Red5 server and one
NetConnection from user B to the server. A publishes a NetStream which
B subscribes and vice versa (4 streams in total).
Now assume A wants to terminate the chat session. Then A closes his
NetStreams (1 publishing and 1 subscribing NetStream) and closes his
NetConnection afterwards. Pretty straightforward I think. Then the
server application code should handle the session closing, especially
disconnection user B.
In order to achieve this we overloaded ApplicationAdapter.appDisconnect
and ApplicationAdapter.roomLeave. But these event handlers are NOT
invoked for some strange reasons. So our server code does not know
about the connection loss. These event handlers are indeed called later
when the other side (user B) closed his NetStream objects.
This strange behaviour apparently does not occur if we never create any
NetStreams on the NetConnections.
Is this behaviour intended? Is there a special way to _really_ kill the
NetStreams so that the NetConnection is _really_ destroyed and we get
We currently use Red5 v0.6 rc2 on a Windows machine. We tried trunk,
but the current trunk failed at startup throwing some exception.
Red5 mailing list
Red5 at osflash.org
__________ NOD32 2157 (20070330) Information __________
This message was checked by NOD32 antivirus system.
More information about the Red5