You can clone with
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.
Isn't this a duplicate with #56 ?
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.
Support for deferred (background) snippet execution, closed by 297078e
Closed with http://github.com/dpp/liftweb/commit/297078ea712c36024e4d98d47d0c296d3c2cc814
Imported from GitHub: http://github.com/dpp/liftweb/issues/66/find
Imported from Assembla: http://www.assembla.com/spaces/liftweb/tickets/66