if more than one stream is published to a group with the same name, then the data for all of the streams will flow through the group. however, each subscriber to that named stream will select/latch onto just one of them. there's no way to control which one each subscriber selects, though. if they're all active, then the first one from which a subscriber receives any data wins. if the stream onto which a subscriber has latched goes idle, then the subscriber will un-latch and selection will again be up-for-grabs to the first of the streams from which data is received.
each time a subscriber latches onto a new/different stream, you'll get a NetStream.MulticastStream.Reset NetStatusEvent.NET_STATUS event. you won't get one of those if the subscriber un-latches but then reselects the same stream.
if you're concerned with rogue publishers in a group, same name or not, consider adding a publish password to the group specification.
Thanks a lot for your clear, thorough answer.
so if I have 4 streamers in the group and 25 receivers (listeners), will they or will they NOT have issues receiving ALL 4 streams?
if the 4 streams each have different names, you can make 4 NetStreams for the same group/groupspec and play one of the streams in each. regardless, all 4 streams will pass through every peer, so if your application isn't going to show all 4 streams simultaneously, they should probably be in separate groups.
if the 4 streams each have the same name, then each receiver will select at most one of them to display to the user, but all 4 will pass through each peer.
if that's not what you meant, please be more specific about what you mean by "issues".
Mike Sorry for my question not being clear, however I believe you answered it for me clearly enough
So what do i have to do so that all participants can broadcast and receive streams at the same time...
I mean if there are 4 users in a netgroup, is it possible for each user to broadcast his stream and receive the other 3 streams at the
yes, as long as each stream has a different name. you can watch for the NetGroup.MulticastStream.PublishNotify/UnpublishNotify events to see what streams are available in the group and adapt dynamically.
note that in the N:N case, where everyone in the group is publishing and subscribing, it's more efficient to use DIRECT_CONNECTIONS, since the same amount of stream bandwidth (on average) needs to flow AND you can eliminate the group and multicast stream overhead.
So by listening to the publishnotify event I should be able to get the stream name right??
And how should i go about the Direct_Connections method if I dont know the peer ids of the group members...
Right now I am just creating a new NetGroup for each user and publishing his stream in that netgroup and at the same time listen to the incoming streams coming from the other netgroups. I know that the process in not proper but I am not sure how to do it with direct connections....
Thanks for your help..