vibrant wrote: > While we're at it - can you give examples of sites working on > weblocks?
Besides Thanandar there is, for example: http://www.aulapolska.pl/ http://www.oddsknockout.com/ https//www.lamsight.org/ > Thanandar is written fully in weblocks and CL? Yes. > Any hints on how to do it? Or maybe someone already experimented with > this? I don't know of any working implementation. Best to ask on the Hunchentoot list for this. This is also a task that is well-suited to hiring an external developer. >> However depending on the number of long-polling clients and on >> whether you have a 32 or 64 bit machine you might have to write >> an alternative to the thread-based taskmaster in Hunchentoot. > > Ack. At this point performance doesn't matter but it's good to have > such a simple solution handy. It's not a performance problem. But your Lisp image has a thread limit after which it won't be able to spawn new threads. >> > 2. what is the ORM/database layer that is preferred for weblocks and >> > consistent with it's design patterns and core ideas? >> >> It depends on the project. We have backends for Elephant (OODB), >> Prevalence (persistent in-memory database), Postmodern >> (Postgres ORM) and CLSQL (generic SQL ORM). > > What are the experiences of users with Elephant? It seems pretty > unmaintained (last update from 2009?). Impossible, I just pushed a new patch to Elephant this morning. :) LAMsight above is successfully using Elephant as backend. > And my past experiences were > that in the end you always have to resort to a SQL DB in order to > generate statistics from the data and more complicated queries and so > on. But maybe Elephant is different and it's not a big deal to create > a functioning system in it? That totally depends on the nature of your queries, the structure of your data and the size of your data. Leslie -- You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/weblocks?hl=en.
