0
[Deprecated] Client Server protocol draft
jonte edited this page 2011-02-02 11:10:54 -08:00
This is a proposition for the client -> server communication protocol. The idea is that we need to be able to define and call functions, and the very least.
Client -> Server
| Token | Command | Argument size | Arguments | Description |
|---|---|---|---|---|
| __hello | 0 | |||
| <#ref_num> | __echo | optional message | ||
| <#ref_num> | __define | "JavaScript" | ||
| <#ref_num> | __start | |||
| <#ref_num> | __stop | optional message | ||
| lt;#ref_num> | __boot | <#ref_num> <#ref_num> | ||
| <#ref_num> | __error | optional message | ||
| <#ref_num> | COMMAND | optional message |
Server -> Client
Here the <#ref_num> is the clients own <#ref_num>.
| Token | Command | Argument size | Arguments | Description |
|---|---|---|---|---|
| <#ref_num> | __ok_hello | |||
| <#ref_num> | __ok_echo | optional message | ||
| <#ref_num> | __ok_define | "JavaScript" | ||
| <#ref_num> | __ok_start | |||
| <#ref_num> | __ok_stop | optional message | ||
| lt;#ref_num> | ___ok_boot | <#ref_num> <#ref_num> | ||
| <#ref_num> | __error | optional message | ||
| <#ref_num> | COMMAND | optional message |