Re: [elephant-devel] Advice on multiple deploying multiple applications/repositories

2009-02-07 Thread Clinton Ebadi
Ian Eslick writes: >> > I thought we could just have a single Lisp instance for all the >> > applications we wanted to deploy, but am confused as to how a single >> > Elephant instance could handle multiple stores, one for each >> > application, or better yet, what would be the most advisable >>

Re: [elephant-devel] Advice on multiple deploying multiple applications/repositories

2009-02-06 Thread Ian Eslick
JD, Probably not the right forum for a detailed discussion of this, although many Elephant users do deploy it in a web application environment. I currently use Weblocks for a significant application and can say that it still has some significant warts, particularly in the navigation model

Re: [elephant-devel] Advice on multiple deploying multiple applications/repositories

2009-02-06 Thread John
Thanks for the prompt response. We hadn't actually looked at any web frameworks per se. Our intention is not to develop our own. Instead have read up a little on weblocks, ucw, kpax, kanamit, and hunchentoot. Our goal is to set up two different layers on Lisp code (maybe different machines for eac

Re: [elephant-devel] Advice on multiple deploying multiple applications/repositories

2009-02-06 Thread Ian Eslick
The answer to this depends on the web framework you are using. A simple answer is to dynamically bind *store-controller* for each app for each request/thread. Since each thread will have its own binding, each is tied to a particular application. If you put all your database IO into a with-tr