We are working on a web-based application which is based on MVC
pattern with
servlets as controllers, a relation package ( which corresponds to the database bean ) and for view in place of
JSP we are using PerlUtil5 class and creating templates and doing pattern matching for final display to the browser.
Now whenever we speak about a web application, we have some number of servlets which governs the functionality of the buisness-logic and they execute with-in the web-container.Now the architecture proposed here has one common gateway which can be called as the MainServlet which is the entry point to the application.
All my buisness logic is put in
java classes which are called by the Main servlet depending upon the request which in turn connects to Database and gives me the resulset.So we r having only one servlet in our application and this contains all the necessary details like connection pooling,session management,persistent connection,patching templates as per response,etc.
Now I would like to know from the sheriffs as to what are the pros and cons of this architecture, whether it would function as desired, what are the implications if tommorrow I need to add-on distributed web components, or go for n-tier architecture, or multiple app-server, a distributed database which is not the case at present.Whether the same architecture can be implemented if there is a need to make this application distributed.
I would like a very detailed answer to this and if this could be possible why is this architecture not having a mention in by Sun people themselves(perhaps they can answer my query in a best possible manner).
If anyone would like to know more of this architecture , I am availabe at
[email protected] 
