rsation id,
and then have a Map of conversations stored in an ASO.
Jonathan
> -Original Message-
> From: Peter Mihalik [mailto:[EMAIL PROTECTED]
> Sent: Sunday, April 08, 2007 1:22 PM
> To: Tapestry users
> Subject: Re: multi windowed apps
>
> no, no.. i don't t
Also, if you persist all your properties on the client, then
multi-windowed works.
I've been wanting, for a while, to create a more sophisticated
property persistence strategy that supported this use case without
resorting to moving all state to the client.
On 4/8/07, Peter Mihalik <[EMAIL PROTE
Again, I think that's universally handled by the fact that most
browsers share some basic memory space / session data no matter how
many windows you open.
If your session strategy is with cookies (the default) then it will
work. Url re-writing will work the same.
On 4/8/07, Peter Mihalik <[EMA
no, no.. i don't talk about target="whatever".. i mean if i use the
persist annotation can i have only 1 conversation to the page for the
session? eg. can i have only 1 window opened? for example spring webflow
can have an arbitrary number of the same conversations open for the
session. i can indep
Yes - but only in the same way that every web framework does. Change
the target of your link / form to the window you want the result to be
in.
est voila!
On 4/7/07, Peter Mihalik <[EMAIL PROTECTED]> wrote:
hi, does tapestry support multi window applications?
--
pm
---
