RE: HTTP 1.1 Connections
"Sean C. Sullivan" <[email protected]>
| Newsgroups | gmane.comp.java.openamf.user |
|---|---|
| Message-ID | <[email protected]> |
According to the HTTP 1.1 specification:
{{
A significant difference between HTTP/1.1 and earlier versions of HTTP is
that persistent connections are the default behavior of any HTTP connection.
That is, unless otherwise indicated, the client SHOULD assume that the server
will maintain a persistent connection, even after error responses from the
server.
Persistent connections provide a mechanism by which a client and a server
can signal the close of a TCP connection. This signaling takes place using
the Connection header field (section 14.10). Once a close has been signaled,
the client MUST NOT send any more requests on that connection.
}}
URL: http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html
Let's assume that the Macromedia Flash Player is sending valid HTTP 1.1
requests to the server.
The servlet container (Tomcat, Websphere, Weblogic, etc) is responsible
for managing the socket connections and all HTTP communication.
If you have questions about HTTP connections, consult the documentation
from your servlet container vendor.
-Sean
>-- Original Message --
>From: "Sean Dwyer" <[email protected]>
>
>
>Does the Flash Remoting gateway hold onto HTTP requests? Do they persist
>or
>do the connections expire after a certain amount ot time?
>
>Sean Dwyer
>Approach Infinity Media
>416.590.9696 ext. 227
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click