1. OMG Issue

NOT11 — We need default value for DiscardPolicy

  • Key: NOT11-9
  • Legacy Issue Number: 1580
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In the spec we define the DiscardPolicy QoS property, and the various
    settings it can take on. But, we don"t define what the behavior is
    when the property is not set, and we don"t define a value of NONE that
    can be used to disable the DiscardPolicy after it has been set.
    My proposal is to define a new value, say NoOrder, which is the default
    value and means that DiscardPolicy is disabled, so attempts to send events
    to the channel when the buffer is full will fail, rather than have events
    already in the buffer be discarded.

    As a related issue, we may also want to define a DiscardInterval, so that
    if DiscardPolicy does kick in, the algorithm can select more than one
    event from the buffer to discard. This would prevent the channel from
    thrashing between executing its discard algorithm, and receiving new events.
    I"d be interested in comments about this idea, in addition to the proposal
    to define the NoOrder value for DiscardPolicy.

  • Reported: NOT 1.0.1 — Thu, 25 Jun 1998 04:00 GMT
  • Disposition: Resolved — NOT 1.1
  • Disposition Summary:

    No Data Available

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