Re: [wsrp-interfaces] Implementation question

["Mike Caffyn" <mike@netunitysoftware.com>]

Title: Implementation question

Andre,

 

I glad you are asking this very question since the bookmarkability has always been an issue to me. The only safe way is for the url to propagate to the browser, this obviously has issues with length. The other which is for the consumer to create a token for the navigationstate etc and pass that to the browser. But this has an issue of lifetime that the consumer keeps the navigation url. I always assumed user sessions would be the lifetime, but this really doesn't help the bookmark. what good is a bookmark if its only good for the session. If it's not stored against the lifetime of the session what would you use. It seems that anything else would be out of control on the number of urls to store since you would never know when a bookmark was being used by a user.

 

I think this new flag will help, but I'm not sure it actually solves the problem.

 

Mike

----- Original Message -----

From: Andre Kramer

To: wsrp-interfaces@lists.oasis-open.org

Sent: Friday, September 02, 2005 7:03 AM

Subject: [wsrp-interfaces] Implementation question

If I may somewhat abuse this forum for a quick poll on how navigational state is handled in WSRP consumer implementations, wsrp-interfaces being the most active / vocal one:

Do your Portals facilitate saving a WSRP Portlet’s navigational state between end user login sessions? I.e. if I navigate to a remote portlet’s XYZ screen and then log out from the consumer will I actually be able to log in later (go to the page for the WSRP Portlet) and see XYZ if the portlet has saved/encoded “show XYZ” in its navigational state? I know the spec supports this but is it widely implemented / selectable?

If not, do people think this should be supported by a new boolean flag in a portlet’s metadata description: requestingNavStatePersists=true/false?

Also, I will not be able to make the SC call next week so, again, my apologies.

Regards,

Andre