On Wed, Sep 14, 2005 at 09:36:33AM +0200, Ortwin Gl?ck wrote:
>
>
> Apache Wiki wrote:
> >+ * {{{ Jakarta Http Components }}} '''MUST''' be content agnostic.
> >The project '''DOES NOT''' develop components intended to produce or
> >consume content of HTTP messages.
>
> I guess Multipart-MIME is considered transport level.
>
MIME is a transfer encoding not a content encoding (at least imo). So,
we would still be allowed to develop multipart components. This said, I
would rather prefer to migrate multipart related code to Commons Codec.
There's already multipart-codec project in the Commons Sandbox
> >+ * {{{ Jakarta Http Components }}} develops an HTTP connector or a
> >lightweight server component as a reference material to demonstrate
> >the capabilities of the toolset. The said artifacts '''ARE NOT'''
> >meant for production use and are not released as official Apache
> >Jakarta products.
>
> I would rephrase this so it is logically "not client" instead of
> "server" component. This would allow us also to create a proxy
> implementation (which we will need for testing purposes anyway).
>
A full-fledged HTTP/1.1 compliant caching proxy or reverse proxy would
be a major undertaking and should be developed as a separate project.
Let us keep it out of scope for the time being. We simply have no
resources for such a massive effort.
Oleg
>
> --
> [web] http://www.odi.ch/
> [blog] http://www.odi.ch/weblog/
> [pgp] key 0x81CF3416
> finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416
>
> ---------------------------------------------------------------------
> 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]
