#122 – Mismatch with JSR definition of Action
•JSR168 allows state changes in getMarkup()
•WSRP restricts state changes to performInteraction()
•Choices include:
•1. Allow state changes in getmarkup(): impacts other decisions we have made
•2. Require JSR168 Producers map between these protocols. Not clear that this can be done in a deterministic manner.
•3. Relax WSRP requirement to “no state changes may be sent to the Consumer from getMarkup()”. Could also add a statement about desirability of repeated getMarkup() invocations returning the same markup.
•Resolved: Introduce a nonBlockingInteraction(). (perform & performBlocking)
–Correlated: #94 - getMarkup() able to modify/return state
•Resolved: Relax requirement as per #3
•Correlated: #143a – allow all performInteraction() variants to return markup as an optimization
–Resolved: yes