Re: JSR311: gzip encoding
+1
Ryan McDonough wrote:
> Is an @GZip annotation too specific though? The HTTP spec defines more
> than one encoding token, with GZip only being one such value. It might
> be useful to define a @ContentEncoding annotation that takes an array
> of possible string values. For example:
>
> @Path
> @ContentEncoding({"gzip","deflate", "compress'})
> public class Foo {...
>
> The implmentation would then determine the proper encoding method
> based on the Accept-Encoding header.
>
> Ryan-
>
> On Fri, Mar 27, 2009 at 11:25 AM, Paul Sandoz <Paul.Sandoz_at_sun.com
> <mailto:Paul.Sandoz_at_sun.com>> wrote:
>
>
> On Mar 25, 2009, at 9:58 PM, Bill Burke wrote:
>
> It seems to me that most JAX-RS implementations support GZIP
> encoding. Any way we could require it within the
> specification? Also maybe define a @GZIP annotation to
> specify we want to encode the response (of course it would be
> sensitive to the Accept-Encoding header).
>
> In Resteasy we encode the response in GZIP if the
> content-encoding response header has been set. Our @GZIP
> annotation sets the content-encoding header.
>
> It just seems weird to me that there is no portable way of
> doing encoding within JAX-RS.
>
>
> I agree. There are probably a bunch of little cases like this.
>
> Could you log an issue so we can track it?
>
> Paul.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jsr311.dev.java.net
> <mailto:dev-unsubscribe_at_jsr311.dev.java.net>
> For additional commands, e-mail: dev-help_at_jsr311.dev.java.net
> <mailto:dev-help_at_jsr311.dev.java.net>
>
>
>
>
> --
> Ryan J. McDonough
> http://www.damnhandy.com
>
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the
> individual or entity named in this message. If you are not the
> intended recipient, and have received this message in error, please
> immediately return this by email and then delete it.