Author: fhanik
Date: Sun Mar 19 18:38:10 2006
New Revision: 387117
URL: http://svn.apache.org/viewcvs?rev=387117&view=rev
Log:
two sequencer alternatives added to the total order protocol
Modified:
tomcat/container/tc5.5.x/modules/groupcom/to-do.txt
Modified: tomcat/container/tc5.5.x/modules/groupcom/to-do.txt
URL:
http://svn.apache.org/viewcvs/tomcat/container/tc5.5.x/modules/groupcom/to-do.txt?rev=387117&r1=387116&r2=387117&view=diff
==============================================================================
--- tomcat/container/tc5.5.x/modules/groupcom/to-do.txt (original)
+++ tomcat/container/tc5.5.x/modules/groupcom/to-do.txt Sun Mar 19 18:38:10 2006
@@ -58,6 +58,18 @@
this way, if a member crashes, we don't hold the queue, instead we start
over.
- A TotalOrder token, will contain the coordinator uniqueId as well.
- One parameter should be "receive sequence timeout" incase the
coordinator is not responding.
+ - OPTION A)
+ the coordinator doesn't forward the message
+ since the app will not receive the proper error message,
+ instead the sequencer just returns the sequence, then the member itself
sends the message
+ pros: the app will find out if the send failed/succeeded
+ cons: if the send fails, the sequencer is out of sync for the failed
member
+ OPTION B)
+ The coordinator, receives the message, adds on the sequence number
+ then sends the message on behalf of the requesting members
+ pros: sequencer is in charge of the sequence
+ cons: the sequence can become overloaded, since it has to do all the
trafficing
+ the requesting member will not know if the message failed/succeeded
21. Implement a WAN membership layer, using a WANMbrInterceptor and a
WAN Router/Forwarder (Tipi on top of a ManagedChannel)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
