Issues/Resolution

  1. [Rich] Having the Portlet return a newBookmarkID whenever it needs a new one rather than the Consumer always generating a new one would decrease the impact on cacheability of simultaneously returned markup/resources. Note that this reduces the value of the metadata flag to whether or not the Consumer should output a link for generating a bookmarkable URL.

  2. [Rich] An Consumer generated event (wsrp:makeBookmarkable) which is sent to Portlets who have set usesBookmarkID to true OR have returned a newBookmarkID with the semantics of the Portlet updating the Consumer's concept of the Portlet's navigational state would be helpful.

    • [Richard] Why wouldn't it be sufficient to just have such an event and let the portlet keep track of the rest? I.e. portlet stores deltas in its session, event triggers update to navState -> portlet encodes deltas in navState (or the bookmarkID).

Proposal_Comments (last edited 2009-08-12 18:06:26 by localhost)