Re: SoTimeout setting

2003-10-27 Thread Michael Becke
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. T

DO NOT REPLY [Bug 24012] - Ability to ignore (reject) cookies altogether

2003-10-27 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24012] - Ability to ignore (reject) cookies altogether

2003-10-27 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 23988] - Updates to connectionStaleCheckingEnabled docs.

2003-10-27 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: SoTimeout setting

2003-10-27 Thread Dennis Cook
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 uses. Dennis Cook Be

Re: SoTimeout setting

2003-10-27 Thread Oleg Kalnichevski
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 MultiThreadedHttpConnection

Re: SoTimeout setting

2003-10-27 Thread Michael Becke
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 conve

DO NOT REPLY [Bug 24154] - Setting CONNECTION_TIMEOUT and SO_TIMEOUT on a per-method basis

2003-10-27 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24154] - Setting CONNECTION_TIMEOUT and SO_TIMEOUT on a per-method basis

2003-10-27 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

RE: SoTimeout setting

2003-10-27 Thread Kalnichevski, Oleg
> I am a little wary about adding to much configuration functionality to > the connection managers. In my mind the connection managers are only > responsible for managing access to connections. It's up to the methods > and HttpClient to manage use of them Mike, Why do you think that providing

DO NOT REPLY [Bug 24154] New: - Setting CONNECTION_TIMEOUT and SO_TIMEOUT on a per-method basis

2003-10-27 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu

Re: SoTimeout setting

2003-10-27 Thread Michael Becke
I am a little wary about adding to much configuration functionality to the connection managers. In my mind the connection managers are only responsible for managing access to connections. It's up to the methods and HttpClient to manage use of them. My only thought at the moment is to add an

RE: SoTimeout setting

2003-10-27 Thread Kalnichevski, Oleg
Odi, I agree it may pose some threading problems. But we should make a reasonable effort at trying to solve it, as the capability to enumerate HTTP connections would also be required to tackle the following bug as well: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16124 Oleg -Original

Re: SoTimeout setting

2003-10-27 Thread Ortwin Glück
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 source

Re: SoTimeout setting

2003-10-27 Thread [EMAIL PROTECTED]
Hi, sorry for not having introduced myself..My name is Fabio Capannini,it's not the first time I'm writing to this list:I have filed the bug report 23137 and already asked about the possibilty to set different timeouts for different methods on September the 9th. thanks again your work proves re

Re: SoTimeout setting

2003-10-27 Thread Ortwin Glück
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] wr

RE: SoTimeout setting

2003-10-27 Thread Kalnichevski, Oleg
> If I can't modify the timeout for any connections > in the pool, how can I get a connection with a different timeout just for that > thread and not for all of them? All right. That's the real issue here. If my memory does not fail me, we have already discussed it, agreed that it was a limitat

Re: SoTimeout setting

2003-10-27 Thread [EMAIL PROTECTED]
My scenario is the following: I am trying to share the same client between different threads, each of them should execute an http method to an url, possibly the same url. If a timeout occurs for any one of the executeMethod() calls asynchronously executed by the different threads, I would like to

RE: SoTimeout setting

2003-10-27 Thread Kalnichevski, Oleg
> 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 li

RE: SoTimeout setting

2003-10-27 Thread Kalnichevski, Oleg
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

Re: SoTimeout setting

2003-10-27 Thread Ortwin Glück
[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 return

Re: SoTimeout setting

2003-10-27 Thread [EMAIL PROTECTED]
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 ! +--- HttpConnectionM

RE: SoTimeout setting

2003-10-27 Thread Kalnichevski, Oleg
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 obje

Re: SoTimeout setting

2003-10-27 Thread Michael Becke
It would look something like the following: HttpClient client = new HttpClient(); client.getHttpConnectionManager().getParams().setSoTimeout(10); This setting will then effect all connections created using the connection manager associated with the instance of HttpClient. Mike O

SoTimeout setting

2003-10-27 Thread [EMAIL PROTECTED]
Hi, how am I supposed to set the socket timeout for an HttpClient and for different HttpMethods with the new preferences architecture? I don't understand the inheritance scheme: how can HttpMethodParams inherit SO_TIMEOUT from HttpConnectionParams? What is the default value of SO_TIMEOUT for a c

Re: Force redirect in PostMethod

2003-10-27 Thread Ortwin Glück
Magnus Karlsson wrote: First, thanks for the very helpful HttpClient that you have developed. Pleasure... A question around the PostMethod class; the javadoc tells me that according to some RFC it should not be possible to "automatically" follow a redirect when I send posted data to a certain pa

Re: Force redirect in PostMethod

2003-10-27 Thread Roland Weber
Hello Magnus, you can always obtain the location of the redirect in your application and query the page with a new method. Preferably a GET method in that case. The thing with automatic redirection of POST requests (as POST requests) is that information in the request may be sent to a place of wh

Re: Client Certificate Authentication Question

2003-10-27 Thread Ortwin Glück
It just means you need to write your own Socket factory that returns a socked configured with the client certificate! Of yourse you can use HttpClient. Odi Dan Tran wrote: Odi, thanks for the suggestion. Does it mean, I will not be able to use HttpClient at all? Many thanks -Dan ---

Force redirect in PostMethod

2003-10-27 Thread Magnus Karlsson
Hello, First, thanks for the very helpful HttpClient that you have developed. A question around the PostMethod class; the javadoc tells me that according to some RFC it should not be possible to "automatically" follow a redirect when I send posted data to a certain page. However, I need to do