Has anyone had scalability issues with the use of crossdomain.xml and a Flash client?
We’ve got a custom built flash client served by a web page. We are having firewall problems with some of our users, so we set OpenFire up on a separate server running on port 443. However, to go to a separate server, Flash requires crossdomain.xml to be served via a socket. So we’re serving crossdomain.xml from port 80. (not via HTTP but via a OpenFire. We had to modify FlashCrossDomainHandler.java to change the port to 80).
Our problem is that about 1 in 5 attempts by our Flash client to connect fail. Once it connects the server works fine. Looking at the code, I see that the handler for crossdomain.xml is single threaded. We’re hypothesizing this doesn’t handle users connecting at the same time very well.
Has anyone else hit this issue? Would appreciate tips on alternative methods to serve crossdomain.xml via sockets in a high-performance manner. We’re in a classroom environment. We expect situations where dozens of students (if not hundreds) will all try to log in at the same time.