]
Bela Ban resolved JGRP-653.
---------------------------
Resolution: Won't Do
Won't do this, but its graveyard will be 5.0 instead of Future... unless someone
convinces me that the code (in userland) above won't suffice...
The fact this has been dormant for 12 years shows that this feature is not required.
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
Priority: Major
Fix For: 5.0
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