This content has been marked as final. Show 7 replies
I would not think Flex would have such a limitation. What error are you getting, or what adverse condition is apparent? Any simple sample code?
Simple... Create three HTTP requests that take say 30 seconds on the server each and print out a line for each request into a log (server side).
Make sure the server has enough threads to handle all 3 (in my case I can handle 75).
You will notice that 2 threads executed on the server and are waiting while the third never got to the server until one of the first two is done.
If you set the timeout of the 3 threads to 35 seconds you will notice that 1 will always time out. The one that never reached the server until the first two executed.
I think this is a browser limitation (I found 1 reference to this somewhere on the internet) but need to confirm.
The problem is that our application needs lots of server communication and this is causing a serious problem where many requests time out because they can't reach the server in a timely manner.
Are you sending these requests from the same component instance?
If so, all subsequent calls are cancelling the previous calls to the same HTTPService object.
Each time we need data we create a new HTTP request object. We don't reuse them.
Hmmm.... I can see that there are around 8-12 requests sent one by one in my application without any problem.
Browser - FF/IE/Safari.
Servers - Apache 1/2
Did you try to use WireShark or any other sniffer to check the traffic?
WireShark? Ill check it out. This can definitely help.
you usually have a limitation from your browser.
In firefox you can check your config by typing about:config in the URL
check network parameters (network.http.max-connections-per-server & others)
This is a client parameter, not controlled by flex or your server.
multiple virtual host on the same server can increase that but can also increase complexity.