You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2008/03/20 19:37:24 UTC

[jira] Created: (HBASE-535) REST servlet should allow content bodies to be gzipped, incoming or outgoing

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

                 Key: HBASE-535
                 URL: https://issues.apache.org/jira/browse/HBASE-535
             Project: Hadoop HBase
          Issue Type: New Feature
          Components: rest
            Reporter: Bryan Duxbury
            Priority: Trivial


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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (HBASE-535) REST servlet should allow content bodies to be gzipped, incoming or outgoing

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-535.
-------------------------

    Resolution: Won't Fix

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

> REST servlet should allow content bodies to be gzipped, incoming or outgoing
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-535
>                 URL: https://issues.apache.org/jira/browse/HBASE-535
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: rest
>            Reporter: Bryan Duxbury
>            Assignee: Andrew Purtell
>            Priority: Trivial
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HBASE-535) REST servlet should allow content bodies to be gzipped, incoming or outgoing

Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HBASE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12746569#action_12746569 ] 

Andrew Purtell commented on HBASE-535:
--------------------------------------

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. 



> REST servlet should allow content bodies to be gzipped, incoming or outgoing
> ----------------------------------------------------------------------------
>
>                 Key: HBASE-535
>                 URL: https://issues.apache.org/jira/browse/HBASE-535
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: rest
>            Reporter: Bryan Duxbury
>            Assignee: Andrew Purtell
>            Priority: Trivial
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.