#45 - Signaling state change in InteractionResponse
•How “sticky” is navState? Extremes = zero and Consumer-user session.
–Consumer manages navState in a manner that allows the user to get the same page for the duration the Consumer chooses (at a minimum for the Consumer’s page).
•Does a null mean keep current (v0.8 semantics) and thereby require the Consumer to manage this between user invocations or does it mean no state? Even in the second case, the Consumer MUST remember the last navState (for example) in order to properly handle a page refresh.
–Make navState required (null not available) … bookmarking comment