Overview¶

Functional properties:¶

• Event-driven middleware with broadcast semantics
  • Additional patterns implemented on top of this base functionality
• logically unified bus across multiple transports
  • currently a spread-based and an in-process transport are available
• Bus is structured by hierarchical channels
  • / receives all messages of sub-scopes like /a/test

Non-functional properties:¶

• lightweight:
  • small dependency footprint for the core layer
  • Targeting at embedded systems (e.g. Nao)
• Languages: cpp, java, python, common lisp
  • real implementations, no bindings to provide natural interfaces in each language
• No single wire type like XML:
  • instead arbitrary client data is serialized to different wire types using (user-installed) converters
    • default set of converters exists (e.g source:/trunk/c++/core/src/rsb/converter/StringConverter.cpp)
  • provide flexible and fast serialization mechanisms
  • XML support layer as additional library

Planned functionality:¶

• naming and discovery
• introspection tools
• model-based setup