F2F | Documentation | Messages
F2F soft nodes communicate by passing f2f:messages, which may be of 18 different types:
| Type | Direction | Acknowledgement | Description |
|---|---|---|---|
| down | downstream | The most important downstream type. When a service is requested that is not available at a soft-node, a 'down' packet is created in which to send the request. | |
| down-ok | upstream | Yes | |
| send | downstream | The second most important downstream type. Made by CORE/send{,-internal} sends a packet to a particular soft-node. | |
| send-ok | upstream | Yes | |
| send2 | downstream | Send to a process and resolved to listeners | |
| send2-ok | upstream | Yes | |
| signal | downstream | Not currently used. Needed for process control | |
| signal-ok | upstream | Yes | |
| term | upstream | The most important upstream type. When a thread terminates, a 'term' packet is used to send the results back to the creator. | |
| term-ok | downstream | Yes | |
| return | upstream | The second important upstream type. Made when CORE/return explicitly sends data back upstream to the originator of the thread. | |
| return-ok | downstream | Yes | |
| register | upstream | Not currently used. Notify a process of a listener | |
| register-ok | downstream | Yes | |
| unregister | upstream | Not currently used. Notify a process that a listener stopped listening | |
| unregister-ok | downstream | Yes | |
| update | upstream | Data which is return back to processes. | |
| update-ok | downstream | Yes |
Generated 2009-07-19 08:45:08 Europe/London from a docbook.xml by F2F Documentation Module.