Roland Weber wrote:
Hi folks,
I don't like the current HttpContext hierarchy. We have:
HttpContext - interface, some attribute name constants
HttpExecutionContext - implementation, more attrib names
SyncHttpExecutionContext - extended implementation
HttpClientContext - more attribute names
We solved this much better with HttpParams, where
all the attribute names are defined separately
instead of cluttering the interface or being spread
around in implementation classes.
I would like to move the attribute name constants
either to separate interfaces defining only constants,
or to isolated classes with static helper methods like
we have them for HttpParams. The HttpContext hierarchy
in core/client would be streamlined to the interface
and the two implementations.
What do you think?
cheers,
Roland
Hack away
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
