CVS update: JGroups/doc/design DataCenterReplication.txt

  User: belaban 
  Date: 10/11/08 12:02:53

  Modified:    doc/design DataCenterReplication.txt
  Log:
  new design
  
  Revision  Changes    Path
  1.10      +6 -2      JGroups/doc/design/DataCenterReplication.txt
  
  Index: DataCenterReplication.txt
  ===================================================================
  RCS file: /cvsroot/javagroups/JGroups/doc/design/DataCenterReplication.txt,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- DataCenterReplication.txt	2 Jul 2008 11:24:37 -0000	1.9
  +++ DataCenterReplication.txt	8 Nov 2010 12:02:53 -0000	1.10
  @@ -3,7 +3,7 @@
   ================================
   
   Author: Bela Ban
  -Version: $Id: DataCenterReplication.txt,v 1.9 2008/07/02 11:24:37 belaban Exp $
  +Version: $Id: DataCenterReplication.txt,v 1.10 2010/11/08 12:02:53 belaban Exp $
   
   We have data centers in New York (NYC) and San Francisco (SFO). The idea is to replicate traffic from NYC to SFO
   asynchronously. In case of a site failure of NYC, all clients can be switched over to SFO and continue working with
  @@ -100,4 +100,8 @@
   
   No, doesn't work ! The relay would have to be active on every node ! This is not feasible as this would require
   every node to have a TCP connection to NYC ! We still need to do it on reception not sending. However, messages
  -cannot exclude the sender
  \ No newline at end of file
  +cannot exclude the sender
  +
  +*****************************************************
  +*** UPDATE: this design is continued in RELAY.txt ***
  +*****************************************************
  
  
  

------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a 
Billion" shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev