So what you are saying is if I have 3 httpservice requests send at the same time 2 go out and 1 is queued up. When a result or fault event occurs on one of them then the 3rd service request is sent correct?
How do I know if I am using a persistent connection? I was asking this question earlier, does a Flex application keep the connection alive so that sessions will never timeout as long as the application is running in the browser? Even if the user has is not sending any requests to the server but the first? Sorry don't mean to hijack this thread. On 09 Apr 2007 05:20:37 -0700, Peter Farland <[EMAIL PROTECTED]> wrote:
The maximum number of concurrent HTTP connections allowed to a web server is controlled by the browser. The HTTP 1.1 specification suggests a limit of 2 connections per host, but this requires further consideration if persistent connections are to be used. Some browsers can be configured to accept more, but your users will more than likely have the default settings. IE honors the 2 connections per host suggestion (but to change this you have to edit the registry, see MaxConnectionsPerServer). Firefox sets this value to 8 but does still limit persistent connections to 2 (you can change these settings via about:config). If you were dealing with a closed network or intranet application, you may be able to change your company's IT policy and roll out different default settings, but for public applications I doubt this will be possible. There are lots of other tricks that you can use to optimize HTTP requests (e.g. idempotent GET requests you benefit from pipelining etc)... but my point is that there's a bit more to consider than a bunch of simultaneous requests.
