Changes between Initial Version and Version 1 of Ticket #322
- Timestamp:
- 05/24/10 17:57:56 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #322 – Description
initial v1 8 8 * Exchange name: 'ckan' 9 9 * Exchange type: topic exchange (most flexible) 10 * Routing keys: OBJ_TYPE.OBJ_ID10 * Routing keys: (see below) 11 11 12 === Example routing keys === 12 === Routing detail === 13 Routing key format: "OBJ_TYPE.OBJ_ID.CHANGE_TYPE" 14 (NB tags should be identified by their name, not ID) 15 16 Example routing keys 13 17 * 'package.238bc-704a87-928374.new' - New package created with ID '238bc-704a87-928374' 14 18 * 'group.4234-ab98203-fe324.edited' - Group '4234-ab98203-fe324' edited 19 * 'tag.704a8-2f38bc-928374.' - New package created with ID '238bc-704a87-928374' 20 21 Example queue bindings that clients may use: 22 * * - no filtering - client receives all notifications 23 * package.* - only changes to packages 24 * package.238bc-704a87-928374.* - only changes to a particular package 25 * package.#.new - only packages creations 26 27 === Versioning === 28 Since message payloads will be tied into the REST Entities, it makes sense to join up with the REST versioning. This could be achieved by providing new exchanges called 'ckan-1.1' perhaps? 15 29 16 30 === Documentation ===