Hi Sean, I would have expected the other behavior as the JDK keeps HTTP connections alive by default. There is a system property to change this behavior, you may want to play with it and see what happen: "http.keepAlive (default: true)" http://java.sun.com/j2se/1.5.0/docs/guide/net/properties.html
In this other document they have an interesting paragraph: http://java.sun.com/j2se/1.5.0/docs/guide/net/http-keepalive.html "What makes a connection reusable? Since TCP by its nature is a stream based protocol, in order to reuse an existing connection, the HTTP protocol has to have a way to indicate the end of the previous response and the beginning of the next one. Thus, it is required that all messages on the connection MUST have a self-defined message length (i.e., one not defined by closure of the connection). Self demarcation is achieved by either setting the Content-Length header, or in the case of chunked transfer encoded entity body, each chunk starts with a size, and the response body ends with a special last chunk." So, you may want to ensure that all your request entities (representations) have their "size" property precisely set. Also, feel free to have a look at the implementation classes (just two) to see if our usage of HttpURLConnection could be improved. Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Sean Landis > Envoyé : vendredi 10 novembre 2006 00:24 > À : [email protected] > Objet : Keeping a client connection open > > I noticed that using a Client, that the connection is opened > and closed for > every call. I have a web service client that would like to > hold the connection > open across a series of requests. I can't see how to do that. > I'm using the > ServerServlet, in case that matters. > > Thanks, > Sean
