Fenix network
From Giews
Fenix network is the network of installed Fenix nodes in the world. Nodes and their users share their resources via the Fenix network.
Contents |
[edit] Approaches
- We can build a pilot with Web services and P2P to test the development time and real time performance
- We can cooperate with an University to ask a student to build this pilot
- The discussion can be divided in 2 parts:
- (1) all resources but raster images (webservices technology could be more suitable)
- (2) raster images (P2P technology could be more appropriate)
[edit] TO DO
- Add information about Jaxta
- extend this page
[edit] Requirements
- 1 User can work on local node(local computer) and upload his work to his home node
- 2 User can retrieve list of resources per node available
- 3 User can download resource of any node
- 4 Node synchronizes itself with other nodes during the night (this makes requirement 2 and 3 less important)
- 5 Any resource is downloaded within 10(?)minutes given a bandwidth of 56kb(?).
- 6 Fenix network is as less hierarchical as possible. Rome will maintain the reference list of nodes in the world. But each node will store the list of nodes and can be asked to serve the node list after having it stored(Rome might be under attack).
[edit] Other ideas
In order to fully exploit the potential of a p2p network, also the 'protected' data may be spread around with the same modalities of public ones. Such data should be somehow encrypted, so that unauthorized nodes can't view/edit it. Unauthorized nodes can however help transfer this data from/to other nodes, in the very same way other data is transferred. When a user needs access to protected data, s/he asks the data owner for an 'unlock key' that allows such encoded data to be read (and maybe modified). This key has to be directly transmitted from the data owner to the node (or user) asking access to the data; this transmission can also happen via e-mail. The key may be restricted, so that it only allows data access to a given node (or user, or host).
[edit] Pro
- P2P is fast
- P2P has out of the box a lot of P2P functionality
- Web services is easy and fast to develop
- Integrating the web services with the Fenix security might be easier
[edit] Cons
- P2P has a high learning curve
- With web services the P2P behavior needs to be developed
- P2P is applicable in an application with millions of nodes. Fenix will have maximal hundreds of users
[edit] Options
- P2P Bit torrent
- P2P E mule
- Jaxta
- Web services
[edit] Design decissions on implementation level
- SSL can be used to secure the communication. With a key generator a certificate is generated. Each node or node will have a different certificate. The web service or P2P will ask for the certificate.
- A group spans one or more nodes. Rome will generate the certificate for the group. The group administrator will generate the certificates for intra node communication within a group.
- A decision can be to cancel the group concept. Working only with nodes will reflect more the P2P idea and makes the solution more simple. A group can be made on paper by having one administrator managing for example all Armenian nodes.
