james-mime4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Burrell Donkin <robertburrelldon...@gmail.com>
Subject Re: Content-Location header special code (Robert?)
Date Sun, 27 Dec 2009 18:47:42 GMT
On Sun, Dec 27, 2009 at 5:49 PM, Stefano Bagnara <apache@bago.org> wrote:
> Hi all,
>
> I see there is special code to handle the Content-Location header. It
> seems a special parsing mode has been added to the
> StructuredFieldParser (setFoldingPreserved), during commits to support
> content-location. The very weird thing is that MaximalBodyDescriptor
> calls setFoldingPreserved with a FALSE parameter, that is also the
> default for that class. So in mime4j code no one calls that code with
> "true". As part as another refactoring (fold/unfold consistency) I was
> going to remove that special handling. My readings about the
> Content-Location specs seems to suggest that we just need to remove
> any whitespace after unfolding.

sounds like either an IMAP (or httpclient?) dependency, or a backwards
compatibility thing. so if it's not used in IMAP, feel free to remove
it but the change should probably go into the release notes.

- robert

Mime
View raw message