[JBoss JIRA] Created: (JGRP-563) Consolidate state transfer API to use streams
by Vladimir Blagojevic (JIRA)
Consolidate state transfer API to use streams
---------------------------------------------
Key: JGRP-563
URL: http://jira.jboss.com/jira/browse/JGRP-563
Project: JGroups
Issue Type: Task
Reporter: Vladimir Blagojevic
Assigned To: Vladimir Blagojevic
Fix For: 3.0
Although streaming state transfer has its advantages over byte based state transfer, byte based state transfer is absolutely necessary since streaming based transfer relies on plain sockets that are not firewall friendly. However, that does not mean that we cannot consolidate state transfer API at application level and mask byte based transfer with streams. We have already done this in JBC 2.0 so there is no reason not to do it on JGroups level as well.
Advantages:
- simpler state transfer API
- interchangeable state transfer mechanism without affect on application
- simplification of client application
Disadvantages:
- we break current API by eliminating getState(byte[]) and setState(byte [])
--
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
13 years, 8 months
[JBoss JIRA] Created: (JGRP-567) Add one shot state transfer for multiple substates
by Vladimir Blagojevic (JIRA)
Add one shot state transfer for multiple substates
--------------------------------------------------
Key: JGRP-567
URL: http://jira.jboss.com/jira/browse/JGRP-567
Project: JGroups
Issue Type: Feature Request
Affects Versions: 2.x
Reporter: Vladimir Blagojevic
Assigned To: Vladimir Blagojevic
Currently (2.5) each sub state transfer requires separate state transfer invocation for each sub state. It would be very convenient if we could transfer a list of substates all in one underlying state transfer. This would require introduction of a new method in JChannel API, however we should avoid additional callbacks on application level. Proposed API for additional JChannel method is:
public boolean getState(Address target, List<String> state_ids, long timeout) throws ChannelNotConnectedException, ChannelClosedException;
--
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
13 years, 8 months