Thank you for your response, I started to look into the RequestDispatcher a bit but I'll have to wait until I get home to take some more time looking into it to understand it better. From what I have been modeling so far it seems as if I will need to make a global database with user information and permissons, and then make a separate database for each app with application-specific tables. Is this the correct way to look at it? Will RequestDispatcher help me to join this information and the sessions together?
Again, I thank you for your help! This is my first app(s) with turbine and my script-based background is quite different from this type of modeling. So I would really like to learn it the RIGHT way from the start without having to change bad habits later :) Matt ----- Original Message ----- From: Daniel Rall <[EMAIL PROTECTED]> To: Turbine Users List <[EMAIL PROTECTED]> Sent: Tuesday, January 15, 2002 2:15 PM Subject: Re: singleton vs multiple applications > "Matthew Koranda" <[EMAIL PROTECTED]> writes: > > > I'm mailing this a little funny so I'm not sure if this will be included in the proper thread but this is pertaining to the thread started by Ronan-Yann Lorin titled singleton vs multiple applications. > > > > I was wondering what the final solution was because I am in a similar situation. I am creating one large app that will connect a company with it's suppliers, and also make the information available on the internet (kind of a intranet/extranet/internet solution). It contains quite a few components that seem as though they might be organized better as separate applications namely a global/personal address book, a calendar, a product catalog and so on. I'm not quite sure how these application would interact if they were separate. My biggest concern is the user login/validation bacause even if they could operate separately, they would need the same users and groups. > > > > I had planned on having one main database as the separation of information is not critical, it will all be hosted ansd operated together. > > Run them as separate webapps. You can use RequestDispatcher from the > 2.3 servlet api for inter-app communication. > > -- > 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]>
