Changes between Initial Version and Version 3 of Ticket #587


Ignore:
Timestamp:
24.12.2013 04:16:14 (9 years ago)
Author:
jri
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #587

    • Property Status changed from new to closed
    • Property Resolution changed from to fixed
  • Ticket #587 – Description

    initial v3  
    11This event would be fired once a topic update request (actually a `topic.update()` call) has performed. Note: while the `POST_UPDATE_TOPIC` event is fired several times -- once for the request topic and, in case of a composite topic, once per child topic) -- the `POST_UPDATE_TOPIC_REQUEST` on the other hand is fired only once (for the request topic). 
    22 
    3 A `POST_UPDATE_ASSOCIATION_REQUEST` event should be added as well, with analogous semantics. 
    4  
    5 These events are required in conjunction with #510 (modification date should bubble up to parents/composites). 
     3The `POST_UPDATE_TOPIC_REQUEST` event are required in conjunction with #510 (modification date should bubble up to parents/composites).