... | ... | @@ -20,4 +20,4 @@ Hence the following is true: |
|
|
* Frames can only be flushed once to transmit.
|
|
|
* Flushed status applies to received frames, these are effectively already flushed.
|
|
|
|
|
|
**Question: How does a persistent state mechanism work?** Does a flushing frame change persistent state or do only received frames cause the state to update? It should be the case that the state accessed via a frame is the same as that in which the frame was generated prior to its flush. There are therefore two states: 1) the current state used when forming and flushing new frames, and 2) the state as received. |
|
|
\ No newline at end of file |
|
|
**Question: How does a persistent state mechanism work?** Does a flushing frame change persistent state or do only received frames cause the state to update? It should be the case that the state accessed via a frame is the same as that in which the frame was generated prior to its flush. There are therefore two states: 1) the current state used when forming and flushing new frames, and 2) the state as received. In creating a new frame, received state changes are applied to the sending state for use in that frame, those changes also being marked as changes in that state. In flushing the frame the sending state is modified. How are loops prevented? |
|
|
\ No newline at end of file |