Since i am using Flex there is no stop() method on NetStream objects, maybe
NetStream.dispatchEvent(new Event("stop")) could do, i tryed .close() and
.play(false) without success...anybody managed in Flex?tnx, Gregor -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nankun Huang Sent: Wednesday, January 17, 2007 7:01 PM To: [email protected] Subject: Re: [Red5] NetStream BadName It was mentioned to me that this behavior is due to the fact that after step c), Client 2 is still playing the client 1's stream published in step a). In order to work around this problem, you'll need to get client 2 to stop subscribing to the stream first ( I used Netstream.stop() ). I don't know if the unsubscribing to a stream occurs automatically after a client stops publishing, but using NetStream.stop() on the subscriber side seems to do it for me. On 1/17/07, Gregor Rot <[EMAIL PROTECTED]> wrote: > I already know somebody was writing about it but still i would like some > information on this: > > a) client1 publishes a stream: > > client1stream.publish("mystream"); > > b) another client starts playing the stream of client 1 > > client2stream.play("mystream"); > > c) client1 disconnects > > d) client1 reconnects and republishes the stream, but gets: BadName. > > Is the plan to change this behaviour in future versions? I downloaded and > compiled the latest 0.6 from the trunk today, but... ;-( > > tnx, > Gregor > > > > _______________________________________________ > Red5 mailing list > [email protected] > http://osflash.org/mailman/listinfo/red5_osflash.org > _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
