I'd really not want to force httpclient to only be a single jar - that
sounds pretty ugly, and really limits the ability for httpclient to reuse
existing code.
Does SequencedHashMap really not add a new feature - the ability for
headers to be retrieved in order?
?
--
dIon Gillard, Multitask Consulting
Work: http://www.multitask.com.au
Developers: http://adslgateway.multitask.com.au/developers
jsdever wrote on 04/09/2002 11:09:50 AM:
> I see your point.
>
> I really would like to use this SequencedHashMap, and become more
> familar with the commons-collections. There are some alternatives.
>
> 1) We could include the commons-collections.jar into the
> commons-httpclient.jar. This might lead to class loader problems and
> would be a large waste.
>
> 2) We could just include the parts of collections (just that one class
> hopefully) in httpclient. This could be done safely in code form but
> would lead to problems updating it.
>
> Any other suggestions?
>
> -jeff
>
> I would be strongly -1 to do that (although I am not a committer).
> Cactus is using HttpClient and I would hate to have to tell all Cactus
> users
> that they should now add one more jar to all their client side and
> server side classpaths without gaining a single new feature for them.
>
> -Vincent
>
>
> --
> To unsubscribe, e-mail:
<mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:commons-dev-help@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
|