NOT 1.2 NO IDEA Avatar
  1. OMG Issue

NOT12 — Filter evaluation in pull mode

  • Key: NOT12-14
  • Legacy Issue Number: 2554
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: It is unclear from the spec when filters are evaluated in pull mode. For
    suppliers there"s no problem as the filter is evaluated when the event
    is received. On the consumer side, the filter can either be evaluated
    when the event is entered into an internal queue (i.e. when the supplier
    proxy "receives" the event) or when the consumer decides to pull the
    event.

    This is only a problem when a filter constraint contains the $curtime
    reserved run-time variable. Perhaps the most intuitive for a user is
    filter evalution at pull time? However, the implications can be quite
    significant for sequence type consumers when invoking the
    try_pull_structured_events operation. The proxy will have to match all
    required events against the filters - and if there"s not enough events
    all filter results must be discarded.

  • Reported: NOT 1.1 — Mon, 29 Mar 1999 05:00 GMT
  • Disposition: Resolved — NOT 1.2
  • Disposition Summary:

    Added 2 sentences to 5th paragraph after constraints examples in section 2.3

  • Updated: Fri, 6 Mar 2015 20:58 GMT