HBase
  1. HBase
  2. HBASE-535

REST servlet should allow content bodies to be gzipped, incoming or outgoing

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Trivial Trivial
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: REST
    • Labels:
      None

      Description

      We could probably save a lot of network traffic by gzipping our requests and responses to REST when possible. A fair number of client libraries support this feature out of the box, and others could be fairly easily coded to work that way. Our content on requests and responses is probably very compressible, seeing as it is base64 encoded.

        Activity

        Hide
        stack added a comment -

        Does stargate provide this Andrew?

        Show
        stack added a comment - Does stargate provide this Andrew?
        Hide
        Andrew Purtell added a comment -

        Clients can set Content-Encoding to gzip or deflate and use the appropriate encoder and Jetty will just handle it. I expect other servlet containers will do the same.

        Server side if Stargate is deployed as a WAR, the container usually has support for compression of dynamic content. For example, for Jetty: http://docs.codehaus.org/display/JETTY/GZIP+Compression . The user would need to set up the GZIP filter using regular expressions matching on paths. I think this is appropriate. Not all tables/use cases want the overhead. I don't think a REST servlet should force it on.

        Show
        Andrew Purtell added a comment - Clients can set Content-Encoding to gzip or deflate and use the appropriate encoder and Jetty will just handle it. I expect other servlet containers will do the same. Server side if Stargate is deployed as a WAR, the container usually has support for compression of dynamic content. For example, for Jetty: http://docs.codehaus.org/display/JETTY/GZIP+Compression . The user would need to set up the GZIP filter using regular expressions matching on paths. I think this is appropriate. Not all tables/use cases want the overhead. I don't think a REST servlet should force it on.
        Hide
        stack added a comment -

        OK. Marking as 'wont fix' since its a feature containers provide.

        Show
        stack added a comment - OK. Marking as 'wont fix' since its a feature containers provide.

          People

          • Assignee:
            Andrew Purtell
            Reporter:
            Bryan Duxbury
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development