Subject: Re: [wsrp-interfaces] Implementation question
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.