Dan, I will have this problem too. I have a eCRM application I have built that uses parts of Turbine to support an Applet. I will need to host the application for different companies. My problem is more about how to segment their application data. I cannot really allow it to be mixed into the same tables. So I assume the only way to segment the users and their data is to have different instances of the application running and thus different contexts as you describe in 2 below.
I assume that the users you are hosting for don't mind sharing tables with other users? I would be surprised if they did not mind. Most companies I have spoken to want the ability to have easy access ot their data for custodial purposes. Even nightly downloads for their data for security of mind. In your scenario 1 below you would need custom extraction to get a customers own application data out of the database. A better solution would be if you could have one context for Turbine and multiple database instances for the different customer's application data and a single database instance for all user's security(using something similar to the group object in the security system to determine which database was used). Has anybody done somethign like this? David Wynter -----Original Message----- From: Dan Diephouse [mailto:[EMAIL PROTECTED]] Sent: 31 December 2001 18:55 To: Turbine Users List Subject: Re: singleton vs multiple applications 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
