Improve persistent state in stream
Persistent state for a frame is usually sent upon a connection reset. However, it is impossible to know reliably where such state is expected to be received or not. Both sides of the connection could inject state, for example the web service might inject previously saved state, but it might not have any and therefore the local machine might inject defaults.
- which host state has priority and how can we be sure not to randomly mix.
The protocol therefore needs improving to ensure state injection control and ordering. It could be that if the stream was created from the web service then all state comes from the web service, except where defaults need to be used. The node needs to know when the web service has sent all state.