A friend of mine who worked for Sleepycat told me that the Amazon home page does up to 40 separate queries. Of course, this was at least five years ago, but still.
That would be an option, a fragment that rendered its body in a new/worker thread, with a time limit, and replaced it with a placeholder if not ready in time. Still a ways to go; I have many other higher priority responsibilities. On Mon, Jun 29, 2009 at 12:00 PM, Richard Newman <holyg...@gmail.com> wrote: > > > Finally, I'm looking forward to (at least experimenting with) > > parallel rendering across fragments. The idea of hitting the > > database with N requests across N threads in parallel and assembling > > the result speedily is very promising. > > This is how Amazon (and probably eBay et al) assemble pages. Each of > the boxes you see -- recommendations, your browsing history, etc. -- > are assembled in parallel. If an agent is taking too long to generate > that part of the page, it's simply dropped to keep total page load > time down. I'm sure they do it through some horrible chunk of > procedural code, of course... > > > > -- Howard M. Lewis Ship Creator of Apache Tapestry Director of Open Source Technology at Formos --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
