 |
|
 |
| |
How it works? |
|
| |
The architecture are divided into 3 layers: Services, Protocol, Connections.
|
|
| |
Services |
|
| |
Services are the API interfaces. Data types involved are:
- Message(message service)
- Remote Procedure Call Request(remote procedure call service)
- Remote Procedure Call Response(remote procedure call service)
- Shared Object update(shared object service)
- etc...
|
|
| |
Protocol |
|
| |
All data are wrapped to DataPackages. Each DataPackage has a type. Each type will have a package handler. When specified data package arrived, related package handler will be picked to handler the data. |
|
| |
Connections |
|
| |
DataPackages are sent via socket connections between hosts. Every 2 hosts will have 2 connections to send and receive data package. All hosts are in a multicast group. So the data package can also be multicasted to hosts. |
|
 |
|
 |
|
|
|
| |
Why this one? |
|
| |
Simple. Simple tools can be a firm base of fantastic ideas.
Being bored with using this* kind of APIs? You may simply want this**:
 
|
|
|
|
|
| |
*:Wenger Giant Swiss Army Knife
**:From a still of movie 'From Beijing With Love'. |
|
|
|
|
| |
Limitations in this version |
|
| |
- Only support IPv4
- Only support max 254 hosts.(What? You have a cluster which has thousands of hosts? Please, please hire me, I can make it for you...)
- Only support one instance per host
- All hosts must in one subnet, and the subnet must be a class C subnet.
|
|
|
|
|
