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

Oleg Kalnichevski updated HTTPCLIENT-1218:
------------------------------------------

      Component/s:     (was: HttpClient)
                   Cache
    Fix Version/s: 4.3 Alpha1

BufferedHeader allows for parsing of message headers lazily only if accessed. I 
do not think it would be a good idea to change that. However, it should be 
perfectly fine to replace the underlying implementation with a more 
serialization friendly one in the caching layer prior to serializing the 
message.

Oleg  
                
> Serializibility of HttpCacheEntry and BufferedHeader
> ----------------------------------------------------
>
>                 Key: HTTPCLIENT-1218
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1218
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: Cache
>            Reporter: Alexis
>              Labels: httpclient-cache
>             Fix For: 4.3 Alpha1
>
>         Attachments: httpCacheEntry.patch
>
>
> Current serialization of HttpCacheEntry relies on java.io.Serializable. But 
> not everybody wants to rely on this RPC format, since there are better 
> alternatives -> Kryo for example. I tested it: once the class is registered 
> in Kryo, serialization is 10 times faster and takes up 4 times less bytes.
> Instances of BufferedHeader (which implements FormattedHeader) in the header 
> group are not serialization friendly: Factory is slow and lot's of memory is 
> wasted to generate parsers.
> A header is a plain POJO with a name and a value, nothing more. I'm not quite 
> sure of the point of the FormattedHeader interface.
> - Quick fix is replacing all BufferedHeader with BasicHeader instances before 
> serializing.
> - Long term idea suggestion: If the API wants to keep FormattedHeader would 
> it be possible to allow the API user to disable it?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to