Issue Details (XML | Word | Printable)

Key: DOL-132
Type: Feature Request Feature Request
Status: Open Open
Priority: Major Major
Assignee: Dierk Koenig
Reporter: Dierk Koenig
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

force value change when ServerAttribute.setValue() is called even when the new value equals the old value

Created: 09/Nov/14 06:01 PM   Updated: 09/Nov/14 06:01 PM
Component/s: Communication-Level
Affects Version/s: 0.10
Fix Version/s: 1.0
Security Level: public

Time Tracking:
Not Specified

 Description  « Hide
ATM, when the old value and the new value are equivalent,
  • no value change command (VCC) is sent to the client
  • no server-side listeners are notified.

While this looked ok at first, it can actually happen that a
client attribute has already changed its value and the according change notification is
under way (sits in the client queue or comes later in the server command list).
In this case the VCC should be sent.
We cannot detect this situation, therefore we must always force the value change command.
However, since from the server perspective, the value did not change, we will not notify any listeners.

Shortcutting endless update circles (hysterese) can therefore be done on the client side only .

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.