chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nathan DeGroff (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CMIS-660) GZip Client Compression (Client Bindings SPI HttpUtils class)
Date Fri, 24 May 2013 18:34:22 GMT

     [ https://issues.apache.org/jira/browse/CMIS-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nathan DeGroff updated CMIS-660:
--------------------------------

    Priority: Minor  (was: Major)
    
> GZip Client Compression (Client Bindings SPI HttpUtils class)
> -------------------------------------------------------------
>
>                 Key: CMIS-660
>                 URL: https://issues.apache.org/jira/browse/CMIS-660
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-client-bindings
>    Affects Versions: OpenCMIS 0.7.0, OpenCMIS 0.8.0
>            Reporter: Nathan DeGroff
>            Priority: Minor
>   Original Estimate: 2h
>  Remaining Estimate: 2h
>
> Issue Detected:
>     While using SessionParameter.CLIENT_COMPRESSION, noted on server that compressed
body only passed 10 bytes before connection ended.
> Environment:
>     CMIS Client: Windows 7 Eclipse Project
>     CMIS Client JDK: 1.6.0_32
>     CMIS Server: EMC Documentum
>     Protocol Used: RESTful
> Possible Solution:
>     Noted that the org.apache.chemistry.opencmis.client.bindings.spi.http.HttpUtils.invoke()
method wrapped the HttpURLConnection.getOutputStream() with a GZIPOutputStream().  HOWEVER,
also noted that only flush() was called on the wrapped BufferedOutputStream() before the connect.
 
>     In my local tests when I stream GZIPOutputStream to a file, I get similar 10 byte
results if I only flush() without calling close().  
>     I took my local copy of the client.bindings and added out.close() after the out.flush()
prior to the conn.connect() call and it works for both compressed and non compressed requests

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message