Interesting question. I can't answer
for the IBM implementation, but would note that the user could have bookmarked
the page just before leaving their session and come back via that bookmark.
As to whether the Portlet can require the Consumer to have a behavior that
restores navigational state from a previous user session, I think that
is more properly a characteristic of the Consumer (perhaps even on a per
page basis) and not a characteristic of the components it used to build
its page(s).
Rich
"Andre Kramer"
<>
09/02/05 07:03 AM
To
<>
cc
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
