Re: DESIGN QUESTION

Does the authentication have to happen on a physically separate web server? If you're the maintainer of both of the initial applications then writing an authentication library for use in both applications is certainly less work than maintaining third application for authentication and the communic

Re: DESIGN QUESTION

NFS, Samba, etc. --- rusty bawa <[EMAIL PROTECTED]> wrote: > Thank you for your reply. > I have thought about it, but how can i call a library > residing on another server? I can replicate [by > pushing] libraries to each server when files get > updated, but that looks like a lot of maintenance > w

Re: DESIGN QUESTION

Thank you for your reply. I have thought about it, but how can i call a library residing on another server? I can replicate [by pushing] libraries to each server when files get updated, but that looks like a lot of maintenance work. what do you think? bawa ___

Re: DESIGN QUESTION

Why do you want the two applications to be hitting another web application for this? Wouldn't it be easier (and much faster) to build a module/library for permissions and hook it up to the other two applications? That module would look up users in the same database. Have a class called Gatekeepe

Re: Design question (servlet handling multiple forms)

> I've used this design pattern to good effect on several projects. I have as well. I will be releasing my very simple framework for using Class.forName() to abstract content from templates (as well as abstract action handling...ie: form processing) on under LGPL (L

Re: Design question (servlet handling multiple forms)

Justin Wells wrote: > Use dynamic class loading to your advantage. Create an interface > representing processing of a request--containing the method you > need to call. Create several implementations of it, one for each > way of processing. > > Then create a "reactor" which loads and dispatches t

Re: Design question (servlet handling multiple forms)

Use dynamic class loading to your advantage. Create an interface representing processing of a request--containing the method you need to call. Create several implementations of it, one for each way of processing. Then create a "reactor" which loads and dispatches these handlers. ie: You supply a