On Sep 27, 10:31 am, Naftoli Gugenheim naftoli...@gmail.com wrote:
Do you mean multiple browser tabs? They won't interfere, because which
stateful snippet is used in a given request depends on which is registered in
that request which depends on which function is called which depends on
Naftoli,
thanks for providing these insights into the inner workings of
Stateful Snippets. The mapSnippet solution sounds interesting. I knew
that snippets don't live on when not needed, but assumed that IF one
is alive in the current session, you would always get that one
instance. Hence at
Please bear in mind that this is *first pass* code and nothing
production ready.
Cheers, Tim
On 27 Sep 2009, at 16:10, marius d. wrote:
Please see the lift-wizard project.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the
Do you mean multiple browser tabs? They won't interfere, because which stateful
snippet is used in a given request depends on which is registered in that
request which depends on which function is called which depends on which
function id is in the request query parameters which depends on the
I think what you want is StatefulSnippet. They're lifetime is not the
session--it's as long as you keep it alive.
Basically Lift maintains a registry of stateful snippets in each request. When
a snippet is needed (referenced in a template), if an instance exists in the
registry that instance
On Sep 26, 10:38 am, tiro tim.romb...@googlemail.com wrote:
Hi,
has anyone investigated or built a way to support tabbed browsing when
there is considerable view/workflow state? Or have I missed an elegant
way for this to be done in Lift?
There is a rather recent wizard code in lift that
