Skip to content

Lazy snippet evaluation #66

Closed
dpp opened this Issue Sep 22, 2009 · 6 comments

3 participants

@dpp
Lift Web Framework member
dpp commented Sep 22, 2009

set a flag on snippets that would fork the evaluation of the snippet into a thread pool and then allow the weaving of the responses at page render time. This would be a benefit to systems that need to fork multiple long running threads (e.g., ad servers, etc.) to pull data in.

@mariusdanciu
Lift Web Framework member

Isn't this a duplicate with #56 ?

Marius

@dpp
Lift Web Framework member
dpp commented Sep 22, 2009

No. This is during the render pipeline rather than a snippet that allows the page to render and then push some content after it's been computed. The use case for this is to call an ad server and a "like pages" server during the rendering of a page and have those snippets forked, but they must be joined before the page rendering can complete.

@dpp
Lift Web Framework member
dpp commented Sep 23, 2009

Support for deferred (background) snippet execution, closed by 297078ea712c36024e4d98d47d0c296d3c2cc814

@dpp dpp was assigned Mar 1, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.