Meeting 19.05.2011¶
Topics¶
- CodingGuidelines - Do we need error handlers or always use the event for signalling in the same stream?
- We consider events that can not be deserialized as errors if they show up in the converters.
- To prevent that on generic message channels, respective type filters need to be instantiated in participants filter lists.
- Clients are informed about errors through a simple callback / error handler.
- Distinguish between Converter Failed and Converter Missing
- Add Null-Converter to deserialize nothing, e.g., for logging and replay
- Readers and multiple connectors: we need some threading of there is more than one InConnector
- Initial implementation: synchronized queue with multiple writers
- Evaluate Select concept for this situation
- PluginConcept
- Data types:
- Composites? (dbus)
- Converter mechanism
- TODO Implement wildcard mechanism
- See Types
- CommonLisp Bindings / Implementation
- 0.2 Implementation almost available
- Introspection Mock-Up
- Implemented in Common-Lisp by Jan
- Logging / Replay Activities
- TODO Define minimal feature set
- TODO Evaluate SWIG to connect C++ backends for introspection / naming?
Loading...