[ https://jira.jboss.org/jira/browse/JGRP-908?page=com.atlassian.jira.plugi... ] Sam Hsu updated JGRP-908: ------------------------- Attachment: sump.xml example protocol stack -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-908?page=com.atlassian.jira.plugi... ] Bela Ban updated JGRP-908: -------------------------- Fix Version/s: 2.8 (was: 2.x) Moved to 2.8 to take a look. If interesting, we'll add it to 2.8 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-908?page=com.atlassian.jira.plugi... ] Sam Hsu commented on JGRP-908: ------------------------------ I started with SMACK.java, but yes... no acks, no retransmits, no state transfer, and enough support to run a MuxChannel. Group membership is entirely by whether you heard something from someone (which was why I was using FD_SIMPLE) with no group coordinator. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JGRP-908?page=com.atlassian.jira.plugi... ] Sam Hsu commented on JGRP-908: ------------------------------ ah, yes, funny that... there's probably other stuff from SMACK that isn't used, either... the seqno may be interesting, as an observation about how many messages was lost, or out-of-order, but my higher-level application doesn't rely so much on ordering, or absolute reliability of the transport, as long as the multicast mostly works. think of it as loosely synchronized multi-processor caches that do invalidation at time-of-reference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira