Hi there, this badname functionality wasnt in 0.5. i havnt seen this badname problem with multiple broadcast streams without subscriber. what i experienced is that you cant republish under the same name when there is still a subscriber connected to this particular broadcast stream. example: 1. broadcaster A broadcast stream "test" -----> subscriber B,C,D subscribes to stream "test". 2. broadcaster A broadcast.close() ----------> subscriber B,C,D still connected to stream "test". 3. broadcaster A broadcast stream "test" ----------> badname!!!!! i would suggest that badname is triggert when a second broadcast is published under the same name. I dont know FMS but i guess you do. Is this a bug. what do you think?. In case we can open a ticket at jira! BTW: my workaround is closing also the subscriber netstreams. Republishing the broadcast stream under the same name. The broadcaster sends a notification to the subscribers to reconnect. This will avoid the badname (in this case!). Happy new year. -Adam- ------------------------------------------------------------------------ ----------------------------------------------- private <http://www.versicherungen-abc.info/private-krankenversicherung/private- krankenversicherung-middle.htm> Krankenversicherung >Yeah, its definately a bug with the current CVS build of red5, when I tried to revert back to the old 0.5 final version, it works fine =P >On 1/3/07, Nankun Huang <[EMAIL PROTECTED]> wrote: >> When I try to publish multiple streams into the same room, I keep >> getting the >> >> NetStream.Publish.BadName code even though the streams DO NOT repeat >> in names and the names are all valid strings. I don't know whats >> happening here. The exact same application works find in FMS. >> >> I am using the UUID generator tool in mx.utils.UIDUtil; to generate my >> random stream-names. Can I reuse name of strings which has already >> been deleted? >> >> So far my experience with red5 for any kind of seriously development >> has been full of weird workarounds and bugs =(, >>
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
