hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey Dever <jsde...@sympatico.ca>
Subject Re: FW: [PATCH] PreEmptive authentication setting
Date Mon, 20 Jan 2003 02:31:53 GMT
  Hey Juergen,

the preemptive property can be set programaticly with:
System.getProperties().setProperty("httpclient.authentication.preemptive", 
"true");

But of course this is global in the JVM.  If finer grained control can 
wait until 2.1, then it would be greatly preferable to wait than adding 
some methods now and taking them out again later.  I know of client code 
that uses this property and it is well documented in the Authenticator 
API and as such would have to maintain compatibility into the 2.0 release.

The supplied patch really should be split into the two seperate parts so 
that they can be discussed/decided/applied seperately.

Thanks,
Jandalf

Pill, Juergen wrote:

>Hello,
>
>In this case: Should we apply the patch, which gives the client/application
>the possibility to control the preemptive setting and re-fix those
>getter/setter during the architectural change?
>
>Best regards
>
>juergen
>
>
>
> -----Original Message-----
>From: 	Ortwin Gl├╝ck [mailto:ortwin.glueck@nose.ch] 
>Sent:	Friday, January 17, 2003 16.41 PM
>To:	Commons HttpClient Project
>Subject:	Re: FW: [PATCH] PreEmptive authentication setting
>
>Kalnichevski, Oleg wrote:
>  
>
>>Odi, I also tend to disagree with your idea of making HttpMethod
>>aware of its HttpClient. That would make these two classes tightly
>>coupled which is generally a bad idea. 
>>    
>>
>
>I agree completely.
>
> > Clearly HttpMethod derived
>  
>
>>classes need to know a whole set of parameters that affect their mode
>>of execution. I would rather see HttpClient pass onto its HttpMethods
>>an instance of a configuration class (similar in a way to
>>HostConfiguration class) that define various aspects HttpMethod's
>>behavior.
>>    
>>
>
>Yep. This was discussed here a couple of times and is the point of the 
>new preferences architecture as described in bug 15435:
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15435
>
>  
>
>>Laura, Good point. I just want to suggest we rethink the overall
>>design of the HttpClient once we get release 2.0 out of the door,
>>rather than attempt to patch various shortcomings of the existing
>>design
>>    
>>
>
>Jeff has clearly stated earlier, that this architecture change should 
>happen after 2.0 (so target of that bug is 2.1)
>
>
>
>--
>To unsubscribe, e-mail:
><mailto:commons-httpclient-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail:
><mailto:commons-httpclient-dev-help@jakarta.apache.org>
>
>--
>To unsubscribe, e-mail:   <mailto:commons-httpclient-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:commons-httpclient-dev-help@jakarta.apache.org>
>
>
>  
>


Mime
View raw message