[jboss-jira] [JBoss JIRA] (JGRP-1419) UNICAST: switch from AckSenderWindow/AckReceiverWindow to Table<Message>

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban updated JGRP-1419:
---------------------------

        Summary: UNICAST: switch from AckSenderWindow/AckReceiverWindow to Table<Message>  (was: UNICAST / UNICAST2: combine retransmission for all members)
    Description: 
UNICAST:
- The sender has an AckSenderWindow, the receiver an AckReceiverWindow
- The sender keeps retransmitting until the receiver delivers the message and acks it


Suggestions:
- Similar to NAKACK2, don't use a separate retransmitter for every member (window), but have just 1 retransmitter task scan the message tables and do retransmission
- The sender's AckSenderWindow can also be replaced with a Table<Message>
- Tthe receiver window can be replaced with a Table<Message> as well !

If we can do this, then we have 
- only 1 proven data structure (Table<Message>)
- not 1 retransmitter per window, but 1 for all the windows (saving space) !

  was:
UNICAST:
- The sender has an AckSenderWindow, the receiver an AckReceiverWindow
- The sender keeps retransmitting until the receiver delivers the message and acks it

UNICAST2:
- The sender has an AckSenderWindow (without retransmission) and the receiver a NakReceiverWindow
- The receiver asks the sender for retransmission only if there's a gap
- Stability ensures that the sender doesn't keep messages around forever

Suggestions:
- Similar to NAKACK, don't use a separate retransmitter for every member (window), but have just 1 retransmitter task scan the message tables and do retransmission
- In UNICAST2, Table<Message> can replace the NakReceiverWindow on the receiver side
- In UNICAST2, we can probably also replace the sender's window with a Table<Message>
- in UNICAST, the sender's AckSenderWindow can also be replaced with a Table<Message>
- In UNICAST, investigate whether the receiver window can be replaced with a Table<Message> as well !

If we can do this, then we have 
- only 1 proven data structure (Table<Message>)
- not 1 retransmitter per window, but 1 for all the windows (saving space) !


    
> UNICAST: switch from AckSenderWindow/AckReceiverWindow to Table<Message>
> ------------------------------------------------------------------------
>
>                 Key: JGRP-1419
>                 URL: https://issues.jboss.org/browse/JGRP-1419
>             Project: JGroups
>          Issue Type: Enhancement
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 3.1
>
>
> UNICAST:
> - The sender has an AckSenderWindow, the receiver an AckReceiverWindow
> - The sender keeps retransmitting until the receiver delivers the message and acks it
> Suggestions:
> - Similar to NAKACK2, don't use a separate retransmitter for every member (window), but have just 1 retransmitter task scan the message tables and do retransmission
> - The sender's AckSenderWindow can also be replaced with a Table<Message>
> - Tthe receiver window can be replaced with a Table<Message> as well !
> If we can do this, then we have 
> - only 1 proven data structure (Table<Message>)
> - not 1 retransmitter per window, but 1 for all the windows (saving space) !

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira