Subject: [Rserpool] Intra-Pool State Sharing

From: "Jose Luis Jimenez Ramirez ECE/TL/NB ID-000 Tlf.4061" <[email-masked]>
Date: Fri, 27 Jul 2001 12:20:29 +0200 (MEST)

Hi All,

The more I study the drafts,the more doubts arise :-).

Well, in the Architecture for Reliable Server Pooling draft, it is said:

	3.1.1.  The RSerPool Aware Client
		...............
		...............

	     (4)  If during the file transfer conversation, PE(1,B) fails,
        	  assuming the PE's were sharing state of file transfer, 
        	  a failover to PE(1,A) could be initiated. PE(1,A) 
        	  would continue the transfer until complete.
        	...............
		...............

------------------------------------------------------------------------------------
        	  
a) Should be assumed that all PE's in a Pool are sharing the states of all the
client/server dialogs, to be able for any other PE handle correctly any failure, and
continue giving service to the PU?

b) How could be done the sharing of the state of file transfer?
   Could be suposed that the PE is acting as a PU with the others PE's of the POOL,
   i.e. there's a connection (SCTP) between PE's reporting about the state of this
   file transfer.
   If this correct, and there's 25 PE's in a POOL, it could be needed :
   	1 SCTP assoc between PU<----->PE1 (File transfer).
   	24 SCTP assoc between   PE1<-----PE2
   				PE1<-----PE3
   			        ............
   			        ............
     				PE1<-----PE25 File Transfer State Sharing.

Maybe I'm supposing a lot of things, but can anybody explain how 
Intra-Pool State Sharing can be done without overloading the system.

                   - -
Regards            º º
Jose      --oOOo---()--oOOo--

_______________________________________________
rserpool mailing list
[email-masked]
http://www.ietf.org/mailman/listinfo/rserpool