On Nov 6, 2008, at 7:27 AM, Craig McClanahan wrote:
> I've checked in a first attempt at a
> com.sun.jersey.api.multipart.HeaderValue class, designed to support
> easier ways to build up and parse HTTP header values that might also
> include semicolon-delimited parameter name=value settings. I
> haven't modified any other code in jersey-multipart to use this code
> yet, so everyone can have a chance to review and comment before we
> make any backwards-incompatible changes in the BodyPart API.
>
> Paul, if you find this class and test useful, it might make sense to
> put them in jersey-core instead.
>
There is already general HTTP header parsing code, using a low-level
stream-based parser, but there is only specific immutable header
values represented as Java types (those from JAX-RS and some that
Jersey defines).
I would be inclined reuse this functionality and add the following to
the jersey core:
- An immutable HeaderValue, that represents a single header value (not
a list).
- An immutable ContentDisposition.
Make sense?
As part of the modularization i need to clean up and refactor the
packages:
com.sun.jersey.impl.http.header
com.sun.jersey.impl.http.header.reader
com.sun.jersey.impl.http.header.writer
Paul.