Hi again, to bump the question and clarify it :
for my application I will leave the default NetConnection.maxPeerConnections to 8.
And I want to know how can a suscriber can know if the publisher has already reached the maxPeerConnections ?
Imagine, the suscriber create a recvStream and connect it to the publisher. Do the suscriber get some special NetStatusEvent code to know that it has been rejected because of the maxPeerConnections limit, or do the publisher has to check the maxPeerConnectiosn and do somethign to let the potential suscriber know about ?
Thanks for your help
Just noticed, NetConnection.maxPeerConnections does not seem to make any difference.
Set it to 2, 10 and default(should be 8) and each time been able to connect about 18 peers, as read by NetGroup.neighborCount.
Could this be a bug or am I misunderstanding the purpose of maxPeerConnections ?
maxPeerConnections is only for 1:1 NetStreams (a NetStream created with new NetStream(netConnection, NetStream.DIRECT_CONNECTIONS)). it's a safety limit so that a large number of peers can't connect to you to play a stream you're publishing for DIRECT_CONNECTIONS, since you'd send a separate copy to each subscriber in that mode.
maxPeerConnections isn't used for RTMFP Groups.
Thank you Michael, this makes more sense now.