Glossary » History » Version 10
J. Wienke, 05/16/2011 11:51 PM
| 1 | 1 | J. Moringen | h1. Glossary |
|---|---|---|---|
| 2 | 1 | J. Moringen | |
| 3 | 1 | J. Moringen | * *event payload*: domain object (programming language dependent) that is associated with an event. |
| 4 | 1 | J. Moringen | |
| 5 | 5 | J. Moringen | _Example(C++,protocol buffers,spread): an object of type IplImage*_ |
| 6 | 3 | J. Wienke | * *data type*: the type (programming language dependent) of event payload. |
| 7 | 3 | J. Wienke | |
| 8 | 5 | J. Moringen | _Example(C++,protocol buffers,spread): IplImage* for the example above_ |
| 9 | 3 | J. Wienke | * *wire type*: Data type (programming language dependent?) of serialized representation of event payload (specific for a port type) |
| 10 | 1 | J. Moringen | |
| 11 | 5 | J. Moringen | _Example(C++,protocol buffers,spread): unsigned char*_ |
| 12 | 2 | J. Moringen | * *wire schema*: Layout/structure of serialized representation of event payload |
| 13 | 1 | J. Moringen | |
| 14 | 5 | J. Moringen | _Example(C++,protocol buffers,spread): specified by ImageMessage protocol buffer descriptor_ |
| 15 | 2 | J. Moringen | * *domain->wire converter*: Mechanism that transforms event payloads into data of the wire type that has an interpretation w.r.t. the wire schema. Uniquely identified by the triple |
| 16 | 1 | J. Moringen | ## domain type |
| 17 | 1 | J. Moringen | ## wire type |
| 18 | 2 | J. Moringen | ## wire schema |
| 19 | 1 | J. Moringen | |
| 20 | 5 | J. Moringen | _Example(C++,protocol buffers,spread): AbstractConverter<std::string>?_ |
| 21 | 6 | J. Moringen | |
| 22 | 6 | J. Moringen | _See [[Types]] for a list of well-known wire schema <-> data type mappings_ |
| 23 | 1 | J. Moringen | * *wire->domain converter*: Similar |
| 24 | 1 | J. Moringen | * *notification*: Transport-specific message that contains |
| 25 | 1 | J. Moringen | ** event meta-data |
| 26 | 2 | J. Moringen | ** wire schema |
| 27 | 2 | J. Moringen | ** (wire type, wire schema) representation of payload |
| 28 | 1 | J. Moringen | Note: does *not* contain domain type of event payload |
| 29 | 10 | J. Wienke | * *scope*: descriptor for a channel of the unified bus. The channel is itself hierarchical, hence the scope also reflects this structure. There is a string-based notation for scopes: @/parent/sub/subsubscope/@. A scope is valid if it matches the given regular expression: @/([a-zA-Z0-9]+/)*@ |