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

[Bela Ban (JIRA)]

    [ http://jira.jboss.com/jira/browse/JGRP-653?page=comments#action_12399223 ] 
            
Bela Ban commented on JGRP-653:
-------------------------------

- Receiver gets an abstraction in the form of an NIO selectable channel. Handback object needs to contain sender's and receiver's address. We don't need headers, as the app can write/read additional data directly to the channel

- On the sender side, we have 1 output stream for the multicast address, and N for the unicast destinations. There's an abstraction (StreamableJChannel ?) which allows us to fetch the right output stream based on the destination

- Provide an implementation of blocking method calls based on StreamingJChannel

- Provide a new impl of RpcDispatcher/MessageDispatcher, based on an input and output stream

- How do we send OOB messages (flags in general) ?

> Streaming API for large messages
> --------------------------------
>
>                 Key: JGRP-653
>                 URL: http://jira.jboss.com/jira/browse/JGRP-653
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>         Assigned To: Bela Ban
>             Fix For: 2.7
>
>         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 contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira