You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (JIRA)" <ji...@apache.org> on 2009/07/06 20:23:14 UTC
[jira] Resolved: (HTTPCORE-199) ContentInputStream does not
implement InputStream.available
[ https://issues.apache.org/jira/browse/HTTPCORE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCORE-199.
----------------------------------------
Resolution: Fixed
Patch committed to the SVN trunk.
Oleg
> ContentInputStream does not implement InputStream.available
> -----------------------------------------------------------
>
> Key: HTTPCORE-199
> URL: https://issues.apache.org/jira/browse/HTTPCORE-199
> Project: HttpComponents HttpCore
> Issue Type: Bug
> Components: HttpCore NIO
> Affects Versions: 4.0.1
> Reporter: Galder Zamarreno
> Fix For: 4.1
>
> Attachments: HTTPCORE-199.patch
>
>
> I'm having an issue with ContentInputStream because it does not
> override IS.available() method. Our client code is implemented in such
> way that available() is checked before creating a buffer so that a not
> too big buffer is created. Javadoc for IS.available says:
> * <p> This method should be overridden by subclasses.
> Hence, ContentInputStream should be overriding it. However,
> ContentInputBuffer does to expose the necessary methods to be able
> calculate this but the implementations do have the possibility of
> calculating this, i.e. SimpleInputBuffer. Any chance of improving
> ContentInputBuffer API so that an available() method is added? If so,
> what would be the timeframe for it?
--
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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org