Hi Oleg,

First off, this is awesome. I think this lays out a great framework for HttpClient's future. In-lined below are questions and comments.


COMPONENT STRUCTURE
===================

This is a purely logical distinction. The below listed components may be
distributed separately or as a part of a larger package (jar).

I think we would want both individual component jars as well a monolithic jars for things like http-client.


http-common
-----------

 depends on
   - Java 1.4 (shall we consider 1.5?)

My preference would be for 1.4 unless there is a major feature in 1.5 we cannot live without. I can't think of one at the moment.


- commons-logging (*) (if feasible I'd rather do without this dependency)

If no commons-logging, what would we use instead? UGLI? Something custom?


* HttpFilter interface allowing for request pre-processing and response post-
processing without having to subclass a given HttpRequest or HttpResponse
implementing classes


- HttpFilter interface

Are you envisioning something similar to servlet filters? Would we use this internally to handle cookies, authentication, etc.?


http-cookie
-----------

depends on
- Java 1.2
- commons-logging (*) (if feasible I'd rather do without this dependency)

logging seems to be an issue in general. Whatever we choose, I think we need to be consistent and use the same logging at all levels.


http-auth
-----------

- NTLMScheme class implementing HttpState

This has been discusses in other threads, but do we want to keep NTLM or should we make it dependent on an external package like JCIFS? My preference would be to externalize this feature.


http-client
-----------

 depends on
   - commons-pool (needed? vote?)

We could, but I'm not sure it's necessary.

http-spider

ideas?

Perhaps integration with Lucene for building a search index? Other integration for handling spider results?


http-proxy
--------------------
 depends on
   - Java 1.4
   - geronimo-network (appropriate? better options? vote?)

Don't know anything about geronimo-network. What would this add?

Should we still be called HttpClient? If we have a simple server, a client, a spider, etc., it seems we're more that just a client.

Mike


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to