[
https://issues.apache.org/jira/browse/HTTPCORE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586770#action_12586770
]
Oleg Kalnichevski commented on HTTPCORE-150:
--------------------------------------------
There are certainly pros and cons. How about making buffering optional? Take a
boolean parameter in the constructor and buffer content if the parameter is
true. Also force buffering if #getContent() is called. Stream out live object
if the buffer is not available, otherwise stream out buffered content.
Oleg
> SerializerEntity
> ----------------
>
> Key: HTTPCORE-150
> URL: https://issues.apache.org/jira/browse/HTTPCORE-150
> Project: HttpComponents HttpCore
> Issue Type: New Feature
> Components: HttpCore
> Reporter: Roland Weber
> Priority: Minor
> Fix For: 4.0-beta2
>
> Attachments: httpcore150.patch
>
>
> We need an entity that serializes a Java object, at least in contrib if not
> in proper.
> Every few months there's somebody asking for it. Should be a nice programming
> exercise.
> Deserializing would be nice as well, but seems less important.
> If we put it in core, it's available for everybody but has to use
> java.io.Serializable.
> If we put it in client, it could use generics. Don't know if that is useful
> in this case.
> cheers,
> Roland
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
