Hmmm... this is going to be extremely tricky to do completely on a client
side !
There's way too many possible parameters and you may actually end up hitting
spec
limits (4k max for a URL).
And I'm not even taking into account the possible security issues (a user
may modify
any parameter stored in the client, so the portal should not trust any
bookmarked
values without security checks...).
In short, I don't think you'll be able to solve your issue this way.
Now how I would proceed to offer a similar function is to implement a "save
page"
button link in the portal navigation. This link would call a screen to
specify the page
name and an action that actually serializes the currently loaded PSML for
this session into
a persistent form with the correct page name.
This way you can bookmark the page by using the URL:
http://myserver/jetspeed/portal/page/mysavedpage
And also implement a portal navigation that allows the user to quickly
browse his available
"saved pages".
> -----Message d'origine-----
> De : Pat Ryan [mailto:[EMAIL PROTECTED]]
> Envoy� : jeudi 12 septembre 2002 23:55
> � : Jetspeed Users List
> Objet : bookmarking with portlet state
>
>
>
> I have a somewhat general Portlet design question that I would imagine
> everyone developing portlets must have come across.
>
> We have a page with many portlets on it and we need to support
> bookmarking, so we do not want to store all of the necessary
> data in the
> session ( perhaps this is why others wont have this issue ). When
> portlet1 renders, it has no way of knowing what portlet2
> might need nor
> do I want to couple them in this way.
>
> For example, portlet1 might need the p1_id parameter on its urls and
> portlet2 might need the p2_id parameter on its urls. If I
> click a link
> in portlet2, it will have its data to render the new information, but
> p1_id wont be part of the url and therefore portlet1 will likely not
> render correctly.
>
> We considered something like:
> ## print out all existing parameters as hidden input fields
> #foreach ($key in $data.getParameters().getKeys())
> <input type="hidden" name="$key"
> value="$data.getParameters().getString($key)">
> #end
> but we ended up with duplicate params, or form only params, etc...
>
> As I mentioned, one goal is to allow the user to bookmark the
> page which
> means each portlet could be in different states so I think using the
> session to store information is out.
>
> Has anyone else come across this issue and how have you handled it?
>
> Thanks
> Pat
>
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
