Changes between Initial Version and Version 2 of Ticket #268


Ignore:
Timestamp:
15.06.2012 00:36:37 (10 years ago)
Author:
jri
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #268

    • Property Status changed from new to accepted

  • Ticket #268 – Description

    initial v2  
    1 Currently for every single topic and topic typed accessed through the core application service the respective POST_FETCH hook is triggered. This results in a big number of unnecessary calls. 
     1Currently for every single topic and topic type accessed through the core application service the respective POST_FETCH hook is triggered. This results in a big number of unnecessary calls. 
    22 
    3 The semantic of the POST_FETCH hook should be changed to a PRE_TRANSMIT, that is the hook ist triggered only when a topic (or type) actually leaves the core and is send to the client. This requires the separation of the application layer from the network layer. 
     3The semantic of the POST_FETCH hook should be changed to a PRE_TRANSMIT, that is the hook is triggered only when a topic (or type) actually leaves the core and is send to the client. This requires the separation of the application layer from the network layer.