[jboss-jira] [JBoss JIRA] (JGRP-653) Streaming API for large messages

[Andrea Carboni (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12757117#comment-12757117 ] 

Andrea Carboni edited comment on JGRP-653 at 2/27/13 1:10 PM:
--------------------------------------------------------------

Having a streaming API would be very useful. We are using jgroups as a better alternative than EBJs. The streaming API should be extended to the RpcDispatcher class in order to send an InputStream over the network.
                
      was (Author: acarboni):
    Having a streaming API would be very usefull. We are using jgroups as a better alternative respect to EBJs.
                  
> Streaming API for large messages
> --------------------------------
>
>                 Key: JGRP-653
>                 URL: https://issues.jboss.org/browse/JGRP-653
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.x
>
>         Attachments: JGroupsInputStream.java, JGroupsOutputStream.java, StreamTest.java
>
>
> For large messages, to load the entire payload into memory might be bad because the payload might be bigger than the max memory available. It would be useful to have an API which allows for use of input and output streams, so that large payloads can be read iteratively by a user and streamed out to the cluster via the underlying channel breaking the data in the input stream into chunks, which are fed into the input stream on the receivers side.
> Issues: we have to have 1 input stream per sender on the receiver side, because a stream is always defined between 2 parties (sender, receiver). Maybe something like NIO, where we register interest in a stream, are notified of new streams ('accept()') and get notified when data on any of the stream is available, would be beneficial.
> Demo is attached

--
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