Thank you for replying my questions. I meant HTTP 1.0 connection. You said: " This timeout is often configurable on the server, but is usually something like 10 or 15 seconds. It is almost never longer on even moderately busy servers."
How do I configure timeout on the server side? In my application, depending on the request, responds might take more than 20 minutes, sometimes hours to compute. Unless I can determine how long it takes before the connection timeout and renew the connection, the client may never get the responds from server. Do you know any links that shows me how to setup IIS with apache SOAP? Thank you very much, Hongda -----Original Message----- From: Scott Nichol [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 15, 2002 2:32 PM To: [EMAIL PROTECTED] Subject: Re: Http 1.0 session I'm not sure what you mean by "HTTP1.0 session". Are you talking about the TCP/IP connection, or about sessions that an application server may create? The server closes its end of a true HTTP 1.0 connection when it is done sending the response, and the client closes its end when it is done reading the response. Many clients and servers that send requests and responses claiming to be HTTP/1.0 also support keep-alive, which I believe was originally defined by Netscape. This evolved into the persistent connection feature of HTTP/1.1. A client supporting keep-alive includes the header Connection: Keep-Alive A server that does not support keep-alive does not include a Connection header. A server with keep-alive disabled will return Connection: close In either of these cases, the client will close its connection when the response is read. If the server supports keep-alive, it sends Connection: Keep-Alive [...] Keep-Alive: [...] where [...] is optional stuff to tell the client how long the connection will remain open without any data transmission. This timeout is often configurable on the server, but is usually something like 10 or 15 seconds. It is almost never longer on even moderately busy servers. Apache SOAP does not support persistent connections. Apache SOAP works with IIS, but IIS alone is not enough. Apache SOAP requires a J2EE container (although it only needs Web container features, not EJB), which is not part of IIS. There are a number of J2EE containers that work with IIS. Of course, there are also products like Tomcat or Resin that provide both a Web server and J2EE container. Scott Nichol ----- Original Message ----- From: "Hongda Lin" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 15, 2002 1:18 PM Subject: Http 1.0 session Hi, Does anyone know how long HTTP1.0 session stays alive? I do know HTTP does expires after a period of time. How long is that? Can I set it? Also does apache SOAP work with IIS? Thanks a lot, Hongda -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
