Stratus does not generate or provide the peerID to an endpoint. each endpoint generates its peerID autonomously. the peerID of a Flash Player or AIR endpoint is a cryptographic hash of (among other things) the endpoint's pseudorandomly generated cryptographic credentials (specifically, a DIffie-Hellman public key). neither the IP address nor port are encoded in any way in a peerID.
peerIDs of Flash Player and AIR endpoints are unforgeable, unguessable, and globally unique.
If peer ID is generated at each flash player end point, then how the communication is done between flash player end points.? To aid end point authentication, secure nonces are used, what are these "nonces"?
Does it mean...
-All the flash player end points which are connected to stratus can communicate with each other,if the publisher's and subscribing peers stream name is same.
In Stratus 2.0, it has a feature called "directed routing", the how it is possible to direct the streams only to particular peers?
I want to know all these answers..PLZ
the secure nonces are private, cryptographically pseudorandom strings derived from a P2P session's secret encryption key that can be used to implement advanced authentication systems in ActionScript.
for 1-to-1 communication, a subscriber peer must know the peerID of the publisher as well as the stream name.
for RTMFP groups, the publisher and subscriber(s) must be in the same group and agree on the stream name.
"directed routing" is a mode for sending single messages through a group. it is not a streaming mode. for more information on RTMFP groups, please see the Flash Player 10.1 ASDocs for "NetGroup.sendToNearest()" and watch Matthew Kaufman's session from MAX2009: