OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interfaces message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [wsrp-interfaces] Implementation question

IBM's implementation supports this feature, i.e. bookmarkability and back
button. I.e. we encode the portlets' navstate into the page's state.
Therfor users can use bookmarks and navigate directly to the saved portlet
navstate. The use can also flip between pages with the portlet navstate
When a user logs on back again we present her the default page set up (or
the last page visited - configurable by the user).

I think this is an implementation choice of the consumer whether it decides
to enable back button & bookmarking conveniently. And since this a consumer
design choice I think we can't really force consumer to do this. I would
consider consumers doing this as a nice, gentle and good app :-)
The spec already is designed the way that it enables consumer to support
On the flag: I don't see to much value of the portlet indicating whether it
prefers the consumer to behave conveniently for the end-user.

Mit freundlichen Gruessen / best regards,

        Richard Jacob
IBM Lab Boeblingen, Germany
Dept.8288, WebSphere Portal Server Development
WSRP Team Lead & Technical Lead
WSRP Standardization
Phone: ++49 7031 16-3469  -  Fax: ++49 7031 16-4888
Email: mailto:richard.jacob@de.ibm.com

             "Andre Kramer"                                                
             citrix.com>                                                To 
             09/02/2005 01:03          rg>                                 
             PM                                                         cc 
                                       [wsrp-interfaces] Implementation    

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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]