Constraints have detailed behavioral descriptions (that need to be in the text) defined in class EiConstraintBehavior.
Consider whether a similar set for EiOpt (out) is appropriate.
There are race conditions (and incorrect logic) that could deliver an EiEvent when a VTN is opted out. What should the VTN do? Apply its own opt out schedule and ignore? Or consider whether to execute the event?
Field | Original Value | New Value |
---|---|---|
Description |
Constraints have detailed behavioral descriptions (that need to be in the text). Consider whether a similar set for EiOpt is appropriate. There are race conditions (and incorrect logic) that could deliver an EiEvent when a VTN is opted out. What should the VTN do? Apply its own opt out schedule and ignore? Or consider whether to execute the event? |
Constraints have detailed behavioral descriptions (that need to be in the text) defined in class EiConstraintBehavior. Consider whether a similar set for EiOpt (out) is appropriate. There are race conditions (and incorrect logic) that could deliver an EiEvent when a VTN is opted out. What should the VTN do? Apply its own opt out schedule and ignore? Or consider whether to execute the event? |
Status | New [ 10000 ] | Open [ 1 ] |
Assignee | William Cox [ william.cox ] | Girish Ghatikar [ gghatikar ] |
Resolution |
This is available through the EiMarketRuleSetType associated through the marketContext. Close as fixed. |
Fix Version/s | wd24 [ 10148 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Applied [ 10002 ] |
Status | Applied [ 10002 ] | Closed [ 6 ] |
Are constraints for a simple device? Or at least EiConstraintBehavior? In the case of a smarter device the VEN can respond.
This is a configuration at the VTN for simple devices. Smarter devices can respond; in effect this seems a VEN classification.
Is this part of the configuration database of the VTN and not sent over the wire?