With non-Air players, you can use a Socket to connect to a server. But you can't create a server itself; i.e. you can't write code to bind to a given port and listen for connections. So, in that scenario you cannot connect both swfs directly (you have to use a socket server).
Appartently with Air you can have your app bind to a port and listen for connections, so you can have 2 swfs talk to each other without the need of an extra party. (I say apparently because I've just found out about the ServerSocket class following the link that Henrik posted). Cheers Juan Pablo Califano 2010/5/12 Eric E. Dolecki <edole...@gmail.com> > Huh? > > > http://www.adobe.com/livedocs/flash/9.0/ActionScriptLangRefV3/flash/net/Socket.html > > all I need is readUTFBytes and writeUTFBytes... > > > On Wed, May 12, 2010 at 6:31 PM, Henrik Andersson <he...@henke37.cjb.net > >wrote: > > > Eric E. Dolecki wrote: > > > >> AIR because of the application security sandbox? Would standalone > >> projectors > >> work as well? > >> > > > > They would not, as they lack the needed API. Have a look at the recent > > additions in the flash.net package, all the useful socket features are > AIR > > exclusive. > > > > _______________________________________________ > > Flashcoders mailing list > > Flashcoders@chattyfig.figleaf.com > > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > > > > -- > http://ericd.net > Interactive design and development > _______________________________________________ > Flashcoders mailing list > Flashcoders@chattyfig.figleaf.com > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
