Meetings2012-08-30 » History » Version 2
J. Moringen, 08/30/2012 03:11 PM
converter topic
| 1 | 1 | J. Moringen | h1. Meetings 2012-08-30 |
|---|---|---|---|
| 2 | 1 | J. Moringen | |
| 3 | 1 | J. Moringen | h2. Rename XOPData to XOP? |
| 4 | 1 | J. Moringen | |
| 5 | 1 | J. Moringen | Renaming should not be problematic at this point since there is not much client code. |
| 6 | 1 | J. Moringen | |
| 7 | 1 | J. Moringen | h2. UUIDs of XOPData Objects |
| 8 | 1 | J. Moringen | |
| 9 | 1 | J. Moringen | * "Send" events (which create documents): event id is document id |
| 10 | 1 | J. Moringen | ** Sending participant returns @XOP@ with generated id |
| 11 | 1 | J. Moringen | ** Receiving particpant gets @XOP@ with generated id (internal handler is wrapped around client-supplied and sets @XOP@ id based on event id) |
| 12 | 1 | J. Moringen | * "Update" events |
| 13 | 1 | J. Moringen | ** Sender has @XOP@ form original send, receiver has @XOP@ object with id |
| 14 | 1 | J. Moringen | ** These @XOP@ objects can be used for updates |
| 15 | 1 | J. Moringen | |
| 16 | 1 | J. Moringen | h2. Event Methods |
| 17 | 1 | J. Moringen | |
| 18 | 1 | J. Moringen | Suggestion: change method field to enum |
| 19 | 1 | J. Moringen | |
| 20 | 1 | J. Moringen | h2. Converter |
| 21 | 2 | J. Moringen | |
| 22 | 2 | J. Moringen | Converter disambiguation at participant construction can be problematic. |
| 23 | 2 | J. Moringen | |
| 24 | 2 | J. Moringen | What happens when converters are registered later? |
| 25 | 2 | J. Moringen | |
| 26 | 2 | J. Moringen | This can be tackled partially later when we have the plugin. |