Revisión | b8fad4e4d184005ad3f754d2e9a071b67854a68d (tree) |
---|---|
Tiempo | 2020-03-24 18:57:01 |
Autor | Albert Mietus < albert AT mietus DOT nl > |
Commiter | Albert Mietus < albert AT mietus DOT nl > |
PubSub: small updates (questionnaire, toctree)
@@ -79,7 +79,7 @@ | ||
79 | 79 | implementation of ``Topic``. Then, the runtime of ``t.publish()`` can controlled; even become *RealTime*. |
80 | 80 | |
81 | 81 | Questionnaire |
82 | -------------- | |
82 | +============= | |
83 | 83 | |
84 | 84 | #. Why can the runtime of ``t.publish`` be unbound? |
85 | 85 | |BR| |
@@ -48,4 +48,10 @@ | ||
48 | 48 | write that sensor-routine! Your current module only has use :meth:`pubsub.Topic.publish`, and that future module can |
49 | 49 | get that data using :meth:`pubsub.Topic.subscribe`; easy! |
50 | 50 | |
51 | +Questionnaire | |
52 | +------------- | |
51 | 53 | |
54 | +We have shortly introduced two advantages, now you have to *think* | |
55 | + | |
56 | +#. Are there **disadvantages** to this *design-pattern*? | |
57 | +#. Can you mention some other **advantages**? |
@@ -19,6 +19,7 @@ | ||
19 | 19 | .. uml:: PubSub-newspaper.puml |
20 | 20 | |
21 | 21 | .. toctree:: |
22 | + :maxdepth: 2 | |
22 | 23 | |
23 | 24 | advantages |
24 | 25 | Use |