Adobe Community : All Content - All Communities

Duplicate userID in P2P movie

forums_noreply@adobe.com — Thu, 13 Jan 2011 03:44:51 GMT

I am using the multiuser xtra to create a host movie. When a client connects using the same userID as another client that is already connected, the first user is disconnected. I want to block a duplicate userID form connecting but the odd thing is that the initial userID gets disconnected even before the WaitForNetConnection handler returns true or false for the second userID.

When the connection request comes in I was expecting to be able to check if the userID was already in use, and if it was then deny the second connection. However like I said, the initial conneciton seems to get broken the instant another conneciton request with the same userID comes in.

Does anyone have any experience or suggestions for this?

Network peer-2-peer movie question

forums_noreply@adobe.com — Mon, 01 Oct 2007 14:48:40 GMT

I am using the MUS xtra to make a peer-2-peer game (not using the Shockwave MUS). I have a server projector and a client projector. One player runs the server projector, then everyone runs the client application (including the person running the server). So there are times when the server is sending messages to a client IP address that just happens to be the IP address of the computer that the server is running on.

I would like to understand the 'route' that the message takes in this scenario. Does it stay 'inside' the computer? Does it leave the computer, go to some outside router only to be send back? If so, does this create unneccesary traffic? Would it be better to have the server recognize this scenario and handle it some other way?

TIA

SendNetMessage question

forums_noreply@adobe.com — Mon, 01 Oct 2007 14:33:18 GMT

I am using the MUS xtra to make a peer-2-peer application (not using the Shockwave MUS). I have a server projector and a client projector. Clients can send messages directly to each other using sendNetMessage and addressing the message directly to another user. In some cases I want the message to be handled by the server application. It seems I can have the message received directly by the server if the message recipient is not a valid connected peer. So I set the recipient to just about any string (that does not match a connected user) and the server recieves the message.

Although this works, it seems sort of clunky to me. Is there a proper recipient I should address these messages to or does it just not matter? TIA