Protocol core-GUI » History » Version 7
Greg Burri, 07/30/2009 04:43 PM
| 1 | 1 | Greg Burri | h1. Protocol core-GUI |
|---|---|---|---|
| 2 | |||
| 3 | This page describes the protocol used by Aybabtu for network communication between core and GUI. |
||
| 4 | 2 | Greg Burri | |
| 5 | 7 | Greg Burri | See source:application/Protos/gui_protocol.proto for message details. |
| 6 | 1 | Greg Burri | |
| 7 | !gui_protocol.png! |
||
| 8 | 5 | Greg Burri | |
| 9 | * There's can be many GUI connected to one core. This is not a goal to achieve but it can be easily done with the chosen protocol. |
||
| 10 | * All communication is made on a single TCP connection which is never closed. |
||
| 11 | |||
| 12 | h2. Message types |
||
| 13 | |||
| 14 | There is three types of message. |
||
| 15 | |||
| 16 | 6 | Greg Burri | * _Core -> GUI_ State : The whole state is periodically sent to the GUI, for example each second. |
| 17 | 5 | Greg Burri | * _Core -> GUI_ Event : Some events can occurs asynchronously like a new chat message or a new log entry. |
| 18 | * _GUI -> Core_ Command : The GUI can send commands to the Core to tell it what to do like download this or browse that. It may or not have a respond from the Core depending of the message. |