----- Original Message -----
From: "Dennis Cook" <[EMAIL PROTECTED]>
To: "'Jakarta Commons Developers List'" <[EMAIL PROTECTED]>
Sent: Friday, May 10, 2002 5:01 AM
Subject: RE: HttpClient question.
> I would also propose that the HttpMultiClient and HttpConnection classes
> could use a method of:
>
> void setInterface(java.net.InetAddress)
>
> This mechanism could be used to direct requests on multi-home hosts. The
> lack of this feature in the java.net.URL class is the reason why I started
> looking at the jakarta project in the first place. I have made these
> changes and tested it locally, but I am not sure of the submission process.
I'm also interested in supporting multi-homing, a bit. ;)
Surely, it can be implemented in HttpMultiClient, I think.
Because it should support threading for multi-homing... Hmm...
But isn't enough to only add a single method like setInterface?
Sung-Gu
> -----Original Message-----
> From: Dennis Cook [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 09, 2002 12:44 PM
> To: 'Jakarta Commons Developers List'
> Subject: RE: HttpClient question.
>
>
> Might I suggest that the setting of individual connection properties be
> handled in the HttpMultiClient rather than in the HttpConnectionManager.
> Have the manager create the connection with only host and port, then have
> the client set the proxy info, as it is currently setting the timeout value,
> prior to using the connection in the method.execute();
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 09, 2002 12:37 PM
> To: [EMAIL PROTECTED]
> Subject: RE: HttpClient question.
>
>
> 1) Oops. I added those methods some time ago, but forgot to commit the
> change. Must be old age catching up with me.
>
> 2) Hmmm, hadn't really thought about changing the proxy settings. This is
> the sort of thing you sent once and they don't change. I'll have to think
> about it some.
>
> 3) http://jakarta.apache.org/site/getinvolved.html. In general we try to
> to deal with dummies. :-)
>
>
> Marc Saegesser
>
> > -----Original Message-----
> > From: Dennis Cook [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 09, 2002 2:08 PM
> > To: 'Jakarta Commons Developers List' (E-mail)
> > Subject: HttpClient question.
> >
> >
> > I was just done a quick review the HttpMultiClient,
> > HttpConnectionMgr, and
> > HttpConnection classes and found several inconsistancies.
> >
> > 1) While the HttpConnectionMgr provides methods to define the use of a
> > proxy, the HttpMultiClient completely hides this capablity.
> > This client
> > creates a private instance of the connection manager and provides no
> > accessors or setters to pass on proxy info to it.
> >
> > 2) The setProxyHost() and setProxyPort() methods of
> > HttpConnectionMgr class
> > do not prevent change of values after connections are created
> > and do not
> > reset values on previously created connections.
> >
> > I am new to this concept of public development projects and
> > not quite sure
> > how changes are proposed, debated, accepted, implemented...
> > Does this happen
> > within each project? Is there a "How to be c contributor for
> > Dummies" guide
> > :)
> >
> >
> >
> > Dennis Cook
> > BeVocal, Inc.
> > tel: 408-907-4170
> > fax: 408-745-9533
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
