I thought client persist was via the url not cookies, but as I said I never
really used it.
It might be handy to have a persist that used a URL argument. That's how I
do paging with something like
url?table1.page=1 where table1 is the component id. In the case of tree that
might be
url?tree1.nodes=1,5,7
Perhaps
@Persist("RequestParameter")
The issue is the URL gets too long and bookmarking is iffy since the id can
change.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Does-the-Tree-component-need-to-use-the-session-tp5667428p5667628.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
