hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oleg Kalnichevski <ol...@apache.org>
Subject Re: HLCA: generating followup requests
Date Mon, 07 Feb 2005 15:43:04 GMT
On Mon, Feb 07, 2005 at 03:49:25PM +0100, Roland Weber wrote:
> Hi Oleg,
> > Correct me if I am wrong, essentially you are talking about the
> > 'request' scope (HttpMethodExecutor) and the 'session' scope
> > (HttpClient), not a hierarchy of contexts per se. Do I understand you
> > correctly?
> Yes. I see only those two levels that are needed.
> > I think HttpContext should always be of request visibility, however some
> > specific objects contained in the context may contain information that
> > spans across several request/response pairs, such as CookieStore,
> > AuthState/AuthScheme. Currently I see this as the simplest solution that
> > works, and I like keeping things simple.
> So in order to share data between different contexts/sequences, the 
> context
> has to be (pre-)populated with objects that are present in those other
> contexts as well.


> > What do you think?
> > 
> I think that is a good solution for the problem at hand, and simpler than
> dealing with a hierarchy of contexts. Improves data encapsulation, too.
> Go ahead, I'm with you now :-)
> Btw, I just checked the digest auth scheme to come up with a concrete
> example, and it would have been hell using a hierarchy... ;-)
> Will you update the design document or should I? After giving others
> time to enter this discussion, of course.

I do not want to be seen as usurping the API redesign leads. Do feel
free to go ahead and update the HLCA document, if you like. 



> cheers,
>   Roland

To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org

View raw message