> Wow, how the hell u do that?

Well, start by reading the MU docs and look for information on peer-to-peer 
connections:

<http://www.macromedia.com/support/director/documentation.html>

Scroll down the above page until you see the section for "Multiuser 3.0 Documentation" 
and you'll find links for PDF doc files. If you're using version 2 of the server then 
scroll down a little further and there are docs specific to that version of the server 
and Xtra as well.

The basic technique is this:

- your main "stage" movie must load first and it 
  utilizes the MU Xtra to establish itself as a
  peer host on the local machine

  (getNetAddressCookie, waitForNetConnection, 
   setNetMessageHandler)

- that main movie then does whatever it needs to
  spawn secondary browser windows with client
  "MIAW" movies embedded

  (gotoNetPage to spawn a new window)
  (gotoNetPage to trigger some JavaScript)
  (externalEvent where possible - limited by browsers)

- those client "MIAW" movies load and utilize the
  MU Xtra to connect to the local peer host (the
  "stage" movie) on the local machine

  (getNetAddressCookie,connectToNetServer, 
   setNetMessageHandler)

- once connected to each other the "stage" and "MIAW" 
  movies can exchange messages

  (sendNetMessage, setNetMessageHandler)

All of the above can occur without the need for any external communications occurring, 
there is absolutely no need to worry about the Multiuser Server in this scenario as 
it's just not used at all! :) Each of the above movies must obtain the local machine's 
current IP number and this is obtained via MU Xtra Lingo and can then be used by each 
movie for their connection/hosting attempts.

I've answered this question far too many times recently and have begun working on a 
"Shockwave MIAW Manager" of sorts. First it will be a basic script object that can be 
dropped into each DCR of concern and it will automagically manage the connections for 
you (you simply instantiate the script telling it to be a host or a client and from 
there the connection work just happens for you until you tell it to disconnect). You 
will then be able to use methods of the script object to send messages across movies 
and trigger handlers as needed. I may add some type of mechanism to actually open the 
new browser windows as well, but that is secondary to just implementing a simple MU 
peer-bot type of script object.

When I finish this project I'll be posting it to directordev.com, my goal is to finish 
it by the end of the week. For now hold off on feature suggestions, once I get version 
1.0 finished I'd be happy to give it some tweaks based on suggestions.

Rock on,
Tom
[To remove yourself from this list, or to change to digest mode, go to 
http://www.penworks.com/lingo-l.cgi  To post messages to the list, email 
[EMAIL PROTECTED]  (Problems, email [EMAIL PROTECTED]). Lingo-L is for 
learning and helping with programming Lingo.  Thanks!]

Reply via email to