On Sat, 2005-09-24 at 20:34 -0700, Martin Cooper wrote: > On 9/24/05, Henri Yandell <[EMAIL PROTECTED]> wrote: ... > > * Jakarta Http Components MUST be content agnostic. The project DOES NOT > > develop components intended to produce or consume content of HTTP > > messages. > > > While I understand what you're trying to say here, this wording appears to > preclude some of what is in HttpClient today, namely multipart content > handling. >
Hi Martin, This statement is not accidental. The plan is to factor the multipart content handling out of HttpClient. There's already a project in Commons Sandbox led by Mark R. Diggory <http://svn.apache.org/repos/asf/jakarta/commons/dormant/codec-multipart/> for that end. Unfortunately the project has been dormant for quite some time but the plan is to revive the project at some point, get it graduate from Sandbox and possibly get it merged with Commons Codec proper at some point of time. > > * Jakarta Http Components DOES NOT define a server side API on top of the > > low level transport API. > > > Again, I understand what you want to say. However, I think it would be > better said in terms that make it clear that it is intended for use on the > client side _of the protocol_, since many people are using HttpClient on the > server side today, but as a client to other servers. > Actually we see more and more often HttpClient code used to implement server side of the protocol as well. This statement is primarily to ensure that the project will not sidetrack into developing and _application_ API competing with javax.servlet API. We merely want to provide low level generic transport primitives. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
