olegk wrote:
>
>
> The original plan with regards to the multipart encoding was and still
> is to factor it out of HttpClient and move it to Commons Codec. There is
> already a project to that end [1] which unfortunately got stalled. We
> have never had any multipart decoding / parsing code in HttpClient in
> the first place, so I wanted to approach FileUpload folks with a request
> to contribute their multipart decoding code to Codec to make the
> multipart codec feature-complete.
>
> Commons Codec already provides BASE64 and quoted-printable codecs needed
> for the content-transfer-encoding support. To me it would also make
> sense to develop mulpitart coding / decoding code out of Commons Codec.
>
>
I understand that that makes sense. I am personally not so keen with commons
codec, because it doesn't provide any streaming API's, although there are
plenty of such API's within the ASF, that might be borrowed. I'll keep this
in mind, though.
Thanks,
Jochen
--
View this message in context:
http://www.nabble.com/Handling-content-transfer-encoding-encoding-and-multipart-requests-with-httpcomponents-tf3539561.html#a9887272
Sent from the HttpComponents-Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
