Hi Oleg, > Actually we may also need stackable HttpContexts too. [...] > Just something to think about.
I remember a discussion about parent contexts last year. This has a different twist to it, though. The 'parent' in HttpExecutionContext could be used with client.getContext() for a workaround, to some degree at least. I'll give it some thought. It makes sense to treat the two similar, but context is more tricky since it gets modified, too. I've had a quick look at uses of .setDefaults(). It's mostly request or response parameters that get changed. If extra objects keep the structure, the parameters in the request or response would need to be replaced with the structure. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
