I have a slightly different case, but along the same lines, in which I'm trying to figure out my best option. I have a web application that I am thinking about reselling to several different companies. It will sell as a standalone version and we also will host it for them.
Option 1: Modify the web app to allow multiple companies within in the same context. Pros: one single web application to maintain, less memory and resources than multiple webapps Cons: Doesn't translate easily into a standalone version Option 2: Have several contexts and copies of the webapp in memory: Pros: No modification of my code, more easily resellable Cons: Lots of resources, increased maintenance While we are on the topic does anyone have any thoughts? I'm leaning toward option #1, even thought this will be a major change to associate all my tables with a company. - Dan Diephouse Ronan-Yann Lorin wrote: >Hi, > >I'm new to Turbine and managing to use it in a new project, which will, in >fact include many sub-projects (applications). > >As Turbine use the singleton pattern, how can I run multiple Turbine >applications hosted in the same application server (JVM), all using their >own configuration file ? > >Thanks in advance. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
