Confirmed users
51
edits
Gaia/Architecture Proposal: Difference between revisions
m
→Bridge
m (→Features) |
m (→Bridge) |
||
| Line 261: | Line 261: | ||
The bridge is designed around a Client/Server architecture, where one server can have multiple clients. | The bridge is designed around a Client/Server architecture, where one server can have multiple clients. | ||
''Extra cautious note: both Client and Server are running on the device.'' | |||
The clients can call remote methods on the server, and can subscribe to events. The server API is defined in a separated strict contract file.<br /> | The clients can call remote methods on the server, and can subscribe to events. The server API is defined in a separated strict contract file.<br /> | ||
| Line 272: | Line 274: | ||
The contract for a specific service can have multiple versions in order to allow older clients to works with the newly server code. | The contract for a specific service can have multiple versions in order to allow older clients to works with the newly server code. | ||
Contracts are defined in JS, and lives next to the code that is going to resolve this contract. The type of contexts where this code will run can be decided at runtime, which offers dynamic threading model (See the Threading | Contracts are defined in JS, and lives next to the code that is going to resolve this contract. The type of contexts where this code will run can be decided at runtime, which offers dynamic threading model (See the [[#Threading_Model|Threading model]] section). | ||
Contract example: | Contract example: | ||