Glossary » History » Version 11
J. Wienke, 06/30/2011 02:25 PM
reformat to have anchors to specific entries
1 | 1 | J. Moringen | h1. Glossary |
---|---|---|---|
2 | 1 | J. Moringen | |
3 | 11 | J. Wienke | {{>toc}} |
4 | 1 | J. Moringen | |
5 | 11 | J. Wienke | h3. event payload |
6 | 1 | J. Moringen | |
7 | 11 | J. Wienke | domain object (programming language dependent) that is associated with an event. |
8 | 1 | J. Moringen | |
9 | 11 | J. Wienke | _Example(C++,protocol buffers,spread): an object of type IplImage*_ |
10 | 1 | J. Moringen | |
11 | 11 | J. Wienke | h3. data type |
12 | 11 | J. Wienke | |
13 | 11 | J. Wienke | the type (programming language dependent) of event payload. |
14 | 11 | J. Wienke | |
15 | 11 | J. Wienke | _Example(C++,protocol buffers,spread): IplImage* for the example above_ |
16 | 11 | J. Wienke | |
17 | 11 | J. Wienke | h3. wire type |
18 | 11 | J. Wienke | |
19 | 11 | J. Wienke | Data type (programming language dependent?) of serialized representation of event payload (specific for a port type) |
20 | 11 | J. Wienke | |
21 | 11 | J. Wienke | _Example(C++,protocol buffers,spread): unsigned char*_ |
22 | 11 | J. Wienke | |
23 | 11 | J. Wienke | h3. wire schema |
24 | 11 | J. Wienke | |
25 | 11 | J. Wienke | Layout/structure of serialized representation of event payload |
26 | 11 | J. Wienke | |
27 | 11 | J. Wienke | _Example(C++,protocol buffers,spread): specified by ImageMessage protocol buffer descriptor_ |
28 | 11 | J. Wienke | |
29 | 11 | J. Wienke | h3. domain->wire converter |
30 | 11 | J. Wienke | |
31 | 11 | J. Wienke | 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 |
32 | 1 | J. Moringen | ## domain type |
33 | 1 | J. Moringen | ## wire type |
34 | 1 | J. Moringen | ## wire schema |
35 | 1 | J. Moringen | |
36 | 11 | J. Wienke | _Example(C++,protocol buffers,spread): AbstractConverter<std::string>?_ |
37 | 1 | J. Moringen | |
38 | 11 | J. Wienke | _See [[Types]] for a list of well-known wire schema <-> data type mappings_ |
39 | 11 | J. Wienke | |
40 | 11 | J. Wienke | |
41 | 11 | J. Wienke | h3. wire->domain converter |
42 | 11 | J. Wienke | |
43 | 11 | J. Wienke | Similar |
44 | 11 | J. Wienke | |
45 | 11 | J. Wienke | h3. notification |
46 | 11 | J. Wienke | |
47 | 11 | J. Wienke | Transport-specific message that contains |
48 | 11 | J. Wienke | * event meta-data |
49 | 11 | J. Wienke | * wire schema |
50 | 11 | J. Wienke | * (wire type, wire schema) representation of payload |
51 | 2 | J. Moringen | Note: does *not* contain domain type of event payload |
52 | 11 | J. Wienke | |
53 | 11 | J. Wienke | h3. scope |
54 | 11 | J. Wienke | |
55 | 11 | J. Wienke | 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]+/)*@ |