On Tue, 2003-10-28 at 19:18, Michael Becke wrote:
Mike, this is certainly a possibility. What tortures me is
realization that with this kind of setup HttpConnection (and possibly
HttpConnectionManager) should not have been HttpParams-enabled after
all. My initial plan was to enable the
uses.
Dennis Cook
BeVocal, Inc.
tel: 650-641-1424
fax: 650-210-9275
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 3:13 PM
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Mike, I see what you mean. Still, no matter how I
Dennis Cook wrote:
If I might inject a comment from a users viewpoint. We use HttpClient in our
VXML interpreter. For any given fetch the application developer can provide
a timeout for the fetch. When a method is generated we would need to pass
this timeout down to the connection the method
Mike,
This is a possibility, though I get the impression that people still
want to specify things at the request level.
There are things that people want even though they do not make sense. SO_TIMEOUT on a
per request basis IMHO falls into this category.
The more I think about this the
Kalnichevski, Oleg wrote:
I have (what appears to me at) a fairly straight-forward approach: allow HttpConnectionParams to be created
and customized before physical HttpConnection instance is allocated, when connection manager
allocates a connection it can look corresponding parameter object up
Oleg
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 28, 2003 11:45
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Kalnichevski, Oleg wrote:
I have (what appears to me at) a fairly straight-forward approach: allow
On Oct 28, 2003, at 3:57 AM, Kalnichevski, Oleg wrote:
I have (what appears to me at) a fairly straight-forward approach:
allow HttpConnectionParams to be created and customized before
physical HttpConnection instance is allocated, when connection manager
allocates a connection it can look
I think we are fairly nearly talking about the same thing. The only
possible difference I see is how the instance of HttpConnectionParams
is obtained. My thought is to pass the instance into HttpClient as a
param to executeMethod() or something similar.
Mike, this is certainly a
Mike, this is certainly a possibility. What tortures me is
realization that with this kind of setup HttpConnection (and possibly
HttpConnectionManager) should not have been HttpParams-enabled after
all. My initial plan was to enable the user to enumerate
HttpConnections contained by the
Here's the current hierarchy of preference objects
Global params
!
+--- HttpClient params
!
+--- HttpConnectionManager params
! !
! +--- HttpConnection params
!
+--- HttpMethod params
Logically SO_TIMEOUT parameter applies to HttpConnection
Does it mean that I can't set different timeouts for different methods sharing
the same client?
If not, how can I arrange this?
thanks again
Kalnichevski, Oleg wrote:
Here's the current hierarchy of preference objects
Global params
!
+--- HttpClient params
!
+---
[EMAIL PROTECTED] wrote:
Does it mean that I can't set different timeouts for different methods
sharing the same client?
Exactly. HttpClient manages connections in a HttpConnectionManager. This
can be a pool of connections. A method just requests connections from
that pool, uses it and
Are you sure you want to be able to set different SO_TIMEOUT per method, not per
connection?
Oleg
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 16:54
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Does it mean that I
Do things in the right place.
Odi, the only problem is that there's no way to enumerate HTTP connection managed by a
connection manager. This limitation has already been discussed once, and I sort of
promised the poster (who unfortunately did not introduce him/herself) to take care of
that
different SO_TIMEOUT per method, not per connection?
Oleg
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 16:54
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Does it mean that I can't set different timeouts for different
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 16:54
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Does it mean that I can't set different timeouts for different methods sharing
the same client?
If not, how can I
Maybe you can write your own / tweak existing connection manager in a
clever way. Maybe it's worth thinking about that for some time.
Oleg: I remember now. Still this would probably introduce subtle
threading problems. I am not sure how you want to address that...
HTH
Odi
[EMAIL PROTECTED]
to be able to set different SO_TIMEOUT per method, not per connection?
Oleg
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 16:54
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Does it mean that I can't set different timeouts
Fabio,
I assume you need that feature for your project and you got your
schedule and deadlines. If I were you, I would spend some time and money
to create a patch and try to get it into the trunk rather than just wait
until somebody feels like doing it for you. The good thing about open
-Original Message-
From: Ortwin Glück [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 16:26
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Maybe you can write your own / tweak existing connection manager in a
clever way. Maybe it's worth thinking about that for some time
, Oleg wrote:
Are you sure you want to be able to set different SO_TIMEOUT per
method, not per connection?
Oleg
-Original Message- From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Sent: Monday, October 27, 2003 16:54 To:
Commons HttpClient Project Subject: Re: SoTimeout setting
Does it mean
-Original Message-
From: Michael Becke [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 17:57
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
I am a little wary about adding to much configuration functionality to
the connection managers. In my mind the connection
Mike, Why do you think that providing an ability to enumerate of HTTP
connection would break this pattern?
I think that adding this functionality could be okay depending on the
use. My worry is that it opens up a whole host of possible invalid
uses. This was not the concern I was trying to
Mike, I see what you mean. Still, no matter how I look at it,
socket/connection timeout parameters on the HttpMethod level does not
seem right.
Let's approach the issue from a different angle. You seem to dislike the
idea of exposing HttpConnection objects contained by
BeVocal, Inc.
tel: 650-641-1424
fax: 650-210-9275
-Original Message-
From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 3:13 PM
To: Commons HttpClient Project
Subject: Re: SoTimeout setting
Mike, I see what you mean. Still, no matter how I look at it,
socket
On Oct 27, 2003, at 6:12 PM, Oleg Kalnichevski wrote:
Mike, I see what you mean. Still, no matter how I look at it,
socket/connection timeout parameters on the HttpMethod level does not
seem right.
Yes, I agree. My intention would be to specify connection
configuration on a per request basis.
26 matches
Mail list logo
