Meeting 2011-07-14¶

• Meeting 2011-07-14
  • Protobuf IDL, Serialization and Code Generation
  • XCF Migration
  • Tools
  • XML Support
  • XPath-like Content Matching
  • IDLs and Serialization
  • Event Sequence Numbers (Stefan)
  • Connector Topology (Stefan)

Protobuf IDL, Serialization and Code Generation¶

See attached slides.pdf file for details.

• Structure of Protocol Buffer Messages
• Protobuf IDL
• Protobuf Serialization
• Protobuf Reflection

Robert:

• Wie funktioniert die Reflection mit den Protocol Buffers? Was muss man beachten?
  • IDL ist benötigt. Kann man aber Out-of-band mitschicken.
  • Für Logger ist das in progress,

XCF Migration¶

• Wo macht man die Transformation?
  • Robert: Bridge? API-Emulator?
  • Sebastian: Component-wise?
• Wichtig ggf.: XML Support für einfache Umstellung
• Neue Idee: Minimalistische Bridge (auf Transport-Ebene) für XCF<->RSB

Tools¶

• Logger
  • Filtering
  • Inspection for XML and Protobuf data
  • Handling of IDLs
• Which other tools are required?

• Development Schritte
  • 1. CL Logger als Binary
  • 2. C++ Logger mit Compiled IDL Artefakten aus dem Installationstoolchain

XML Support¶

XPath-like Content Matching¶

IDLs and Serialization¶

• IDLs werden in SVN was offen verfügbar ist gesammelt
• Tagging von Komponenten / IDLs
• Zusätzliche Dokumentation von IDLs
• Offline Export von IDLs im CMake Makro (file://$(prefix) sollte möglich sein)
• GIT? HTTP Export?
• Dokumentation von IDL in der IDL selbst?
• Autogenerierte Doku
• Plus RDF Descriptor?!?
• CMake Makro ...
  • checkt aktuelle Version aus Repository aus
  • installiert in prefix, falls noch nicht im Cache
• Komponentenkatalog wird erstmal ein Datentypkatalog

• Build-process integration
• How to deal with converter code?
  • How does sharing work?
  • Project structure?
  • Converter repository?
  • Converter deployment?
  • Development process?

• Protobuf <-> XML
• Protobuf <-> Domain objects

Event Sequence Numbers (Stefan)¶

Proposal:

• Change Event.id (which currently is a UUID) to a sequence number
• Benefits
  • Cheaper event creation
  • Full event UUID can be generated lazily (e.g with v3 UUID, namespace: participant id, name: event sequence number)
  • Simple ordering checks and fault detection is possible with sequence numbers
• Caveat
  • Which integer width is required to prevent overflows?
  • Are overflows acceptable?

The decision was to implement this. See #421.

Connector Topology (Stefan)¶

deferred