Could that be changed to lift:concurrent or lift:par etc. (see email on 
scala-user from Marting Odersky mentioned the future use of 'seq' and 'par' in 
concurrent collections)?
Why use a different prefix than everything else built in to lift? And 'lazy' is 
arguably not what's happening.

Jeppe Nejsum Madsen<> wrote:

David Pollak <> writes:

> I've added code (it's in review board right now) that will automatically
> farm any snippet with the "do:lazy='true'" attribute set.
> So, <lift:foo/> will execute the foo snippet inline.
> <lift:foo do:lazy="true"/> will execute the foo snippet in parallel and join
> the result back to page before its rendered.

Very nice! In what context is the snippet executed? I assume that
all timeout handling, errors etc should be handled by the snippet just
as in the non-lazy fashion?


You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to