> Actually the new Preferences Architecture is quite neat and great if it all
> works. It is only the HostConfiguration that does not work and I would love
> to figure out why.
>
Vikram,
I believe the problem with HostConfiguration has been fixed in CVS HEAD.
We'd love to hear from you if now y
> Actually the new Preferences Architecture is quite neat and great if it all
> works. It is only the HostConfiguration that does not work and I would love
> to figure out why.
Vikram,
Basically it appears that (1) we assume it should work one way, (2)
whereas you assume it should work quite the
>
>
> > I am testing the new Preferences Architecture before writing about it in
a
> > Book that I am working on. I have spent the whole of today looking at
the
> > source code but could not locate the problem, so it is bugging me now.
It
> > makes sense, the architecture I mean, but it is just not
Original Message -
From: "Oleg Kalnichevski" <[EMAIL PROTECTED]>
To: "Commons HttpClient Project" <[EMAIL PROTECTED]>
Sent: Wednesday, September 29, 2004 10:29 PM
Subject: Re: Problem with Preferences Architecture
>
> Vikram,
>
> I hope what is to follow wi
Hentzen, Rudy wrote:
Does that mean you don't recommend 3.0 for use...u, damm I am boned, I was coding
with it. Hopefully I can change to 2.0.2 quite easily!!
Rudy
No, I (along mit all other committers) really do recommend 3.0 for use
as stated in our release announcement. I am just saying
t: Re: Problem with Preferences Architecture
Vikram Goyal wrote:
> Sorry, I must be missing something, because I don't see it that way. The
> temporary object that you are talking about, methodConfiguration, is used to
> create the MethodDirector object that is used to execute the
Vikram Goyal wrote:
Sorry, I must be missing something, because I don't see it that way. The
temporary object that you are talking about, methodConfiguration, is used to
create the MethodDirector object that is used to execute the request. So it
is passed to the execute call.
Okay. I explain in de
> I am testing the new Preferences Architecture before writing about it in a
> Book that I am working on. I have spent the whole of today looking at the
> source code but could not locate the problem, so it is bugging me now. It
> makes sense, the architecture I mean, but it is just not working r
>
> Vikram Goyal wrote:
>
> > No that is not right either. Because the HostConfiguration is created
using
> > the supplied HostConfiguration in line 389 as you say, the parameters
from
> > the supplied HostConfiguration are used to clone parameters for the new
> > HostConfiguration, so they should
Vikram,
I hope what is to follow will clarify things a little
(1)
===
HostConfiguration host = new HostConfiguration();
host.setHost("www.google.com");
===
These are t
Vikram Goyal wrote:
No that is not right either. Because the HostConfiguration is created using
the supplied HostConfiguration in line 389 as you say, the parameters from
the supplied HostConfiguration are used to clone parameters for the new
HostConfiguration, so they should all be same. See Host
No that is not right either. Because the HostConfiguration is created using
the supplied HostConfiguration in line 389 as you say, the parameters from
the supplied HostConfiguration are used to clone parameters for the new
HostConfiguration, so they should all be same. See HostConfiguration.java
li
Probably that's not the way it is supposed to be. I'll see what can be
done about it.
Oleg
On Wed, 2004-09-29 at 11:53, Ortwin GlÃck wrote:
> Vikram Goyal wrote:
>
> > Hello,
> >
> > I am not sure if this is a bug or I am not running this right.
> >
> > I am trying to get the preferences archite
>
> The problem in your code is, that the host params are not set at all.
> You should add something along the lines of:
> host.setParams(new HostParams(client.getParams()));
>
> Ortwin Glück
That does not seem to be right. I haven't added any Method params either,
but that works. Anyways, even wh
Vikram Goyal wrote:
Hello,
I am not sure if this is a bug or I am not running this right.
I am trying to get the preferences architecture to modify the http.useragent
property at the client level, and then retrieve the value at the method and
host level. The value gets percolated down to the Metho
Vikram Goyal wrote:
Hello,
I am not sure if this is a bug or I am not running this right.
I am trying to get the preferences architecture to modify the http.useragent
property at the client level, and then retrieve the value at the method and
host level. The value gets percolated down to the Metho
16 matches
Mail list logo
