You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Norman Maurer (JIRA)" <se...@james.apache.org> on 2010/11/23 20:15:16 UTC
[jira] Commented: (IMAP-232) Allow to read Content via InputStream
as optional implementation
[ https://issues.apache.org/jira/browse/IMAP-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934982#action_12934982 ]
Norman Maurer commented on IMAP-232:
------------------------------------
Add InputStreamContent interface which extent Content interface. This offers the needed method
> Allow to read Content via InputStream as optional implementation
> ----------------------------------------------------------------
>
> Key: IMAP-232
> URL: https://issues.apache.org/jira/browse/IMAP-232
> Project: JAMES Imap
> Issue Type: Improvement
> Affects Versions: 0.2-M1
> Reporter: Norman Maurer
> Assignee: Norman Maurer
> Fix For: 0.2
>
>
> Often it would be very cool if we could read the Content via an InputStream and not write it to a WriteableChannel
--
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org