Meetings 2012-08-30¶

Rename XOPData to XOP?¶

Renaming should not be problematic at this point since there is not much client code.

UUIDs of XOPData Objects¶

• "Send" events (which create documents): event id is document id
  • Sending participant returns XOP with generated id
  • Receiving particpant gets XOP with generated id (internal handler is wrapped around client-supplied and sets XOP id based on event id)
• "Update" events
  • Sender has XOP form original send, receiver has XOP object with id
  • These XOP objects can be used for updates

Event Methods¶

Suggestion: change method field to enum

Converter¶