Meetings 2011-06-08¶

RSB 0.3¶

• Current state can be released
  • Reply from spread people does not block the release
  • #338 has been resolved

Examples in RSB Wiki¶

• We should have one example (Wiki page) for the following scenario
  • Three participants
  • In-process communication
  • Spread-based communication
  • Configuration for this scenario

• Documentation of binary package installation
  • see #353

• Examples
  • Ideally, examples from repository should be included in Wiki pages as listings
  • Fallback: copy listings from repository into Wiki pages

Presentation of RSB¶

• Future RSB meetings
  • External participants
  • Thu 14:00h

• Framework Comparison Wiki Page
  • #354

• Component List
  • Has to be updated

• Outlook
  • Naming, Service discovery
    • Distributed (e.g. mdns, upnp, etc.)
  • Tools, in particular introspection, logging
  • Platforms
    • Web integration (WebServices)
    • XMPP
    • Mobile devices
    • DNLA (streaming, etc.)
  • Timing
    • Time-informer
      • Clock source
      • Synchronization
    • Associated Patterns
      • Clock-driven behavior
      • Clock-based filtering

#338¶

• RSB 0.3
  • "string" wire-schema means ASCII-string
• Future releases
  • There should be two string types: utf-8-string and ascii-string

Topics¶

• Protocol Buffers
  • Should dictionary keys in meta-data (UserTime, UserInfo) be ASCII- or UTF8-strings?
  • #176 what is meant by TTL in the context of RSB events?
  • When generating multiple notifications for one event, only include meta-data in the initial/final notification?
• Informer Semantics (and Enforcement)
  • Should a client be allowed to send data which is not of the Informer's configured type?
  • Should a client be allowed to send to scopes which are different from the Informer's configured scope?