We already have a crossdomain.xml in our repository and it ships with every release: http://demo.openmeetings.de/crossdomain.xml
Anyhow, you should _not_ need it. There is only a problem if the network testing tool tries to connect to a server different from what it was loading from. But actually the testing tool should connect to the server it has been loaded from. I mean: What do you want to test? The ping time to our infrastructure OR the ping time of the actual setup that the user is really using? So actually your Network testing tool should simply ship with every release of Openmeetings, load similar to our existing app and connect to the server it has been loading from. Sebastian 2012/5/20 German Grekhov <[email protected]> > Hello! > > I develop the network testing tool and my current task is to create the > port availability test. I try to make it using "flash.net.Socket". But when > it connects to some port then the application receives the SecurityError > 2048. As I understand I need to set up some crossdomain.xml file. Does > anybody know how to deal with it? Thank you! > > Best regards, > German Grekhov. > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.openmeetings.de http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
