W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 2001

Client Side API - HTTP Connections

From: <mark@mindnoise.com>
Date: Wed, 31 Jan 2001 06:43:14 -0500 (EST)
To: "www-jigsaw@w3.org" <www-jigsaw@w3.org>
Message-Id: <20010131064385.SM00370@bajor.softcomca.com>
Hello There!

I'm currently using the Jigsaw 2.1.2 Client side API. Unfortunatley 
I'm experiencing intermittent delays in the time required to 
complete requests.

After a whole lot of 'snooping around', I've noticed that HTTP 
Connection aren't been closed correctly. This is causing the next 
HTTP Connection to be delayed. 

Using the client API is it possible or how do I force a Http 
connection to be closed?

Can anyone shed any light on how Jigsaw handles multiple requests 
to the same host. From what I can piece together, an instance of 

HttpBasicServer manages a synchronous connection pool for a 
particular host. 

I think that my problem is been caused because the connection pool 
is full and requests are been qued until a connection completes or 
times out. Unfortunately they are never been released to the pool 
because they aren't closing properly. 

Or maybe I've recently been taking too many drugs, haven't slept 
enough and should go home before I loose my mind.... 

Mark Katha

FYI: I've attached my request code...
        HttpManager manager = HttpManager.getManager();
        Request aRequest = manager.createRequest();
        aRequest.setMethod("GET") ;
        aRequest.setURL(new URL(aUrl));
        Reply aReply = manager.runRequest(aRequest); 

Mail2Web - Check your email from the web at
http://www.mail2web.com/ .
Received on Wednesday, 31 January 2001 08:06:16 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:37 UTC