0.7 Release

We briefly summarized the changes:
  • socket transport
  • documentation

Plans for 0.8 Release

We briefly summarized our plans:
  • switch to
  • use Rosetta Stone Project to get rid of protocol buffers in the core
  • plugins
  • support Python 3

Source/Sink Participants

Source/sink scenarios (e.g. video encoding from log file) without data flow coordination tend to overwhelm the sink, leading to transport-dependent consequences. For Spead, the sink is disconnected from the sessions, for the socket transport the sinks runs out of memory.

Some strategies to cope with the problem:
  • slow down source when sink(s) get overwhelmed
  • drop events in sinks
  • sinks request transmission of data explicitly

One candidate solution:
Introduce specialized source and sink participants which employ a data-flow protocol in parallel to the event-level communication.

ØMQ Transport

Some initial experiment (by Matthias Schöpfer, Jan Moringen) suggest that ØMQ can be used as an RSB transport. The problems discovered so far are:
  • When ØMQ-level TCP transport is used, multiple publishers seem to be problematic.
    As a result, we will concentrate on the PGM transport.
  • Channels can be handled via ØMQ subscriptions