search

google-code-export / sandy-disaster-recovery

Automatically exported from code.google.com/p/sandy-disaster-recovery
2 stars 2 forks source link

Design Network Architecture/API so that Project Clones Communicate by Default #156

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
There is no "One App to Rule them All," and this is no exception.  Ideally, 
this app will show the disaster recovery community how to truly coordinate and 
communicate.  Ideally, the app should include a robust API to share information 
with other applications.

As a first step, the app should be designed communicate with other copies of 
itself by default.Organizations may do their own implementations, as long as it 
communicates non-identifying information with a central server… Everybody 
talks with everybody else.

How should the network topology be designed? Should there be a central server 
that coordinates? Should it be a P2P network topology?  I'm open to ideas; but 
at the least clones of this project should communicate with one another by 
default.

Original issue reported on code.google.com by v...@aarontitus.net on 14 Jan 2013 at 11:11

GoogleCodeExporter commented 9 years ago

Original comment by v...@aarontitus.net on 30 Jan 2013 at 12:42