"Hubert, Cory" wrote:
> Could someone forward me to a resource that talks more about using
> One servlet in Model 2 architecture. I am skeptical about how a large
> application can handle all request through one servlet.
>
The Struts architecture that Martin is looking at is available at
<http://jakarta.apache.org/struts>, and includes a user's guide that discusses the
suggested application architecture.
I'm curious though -- what is it about one servlet versus many servlets that
concerns you? Martin's concerns, as he clarified them, are more around
manageability rather than performance.
Craig McClanahan
>
> -----Original Message-----
> From: Martin Cooper [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, August 24, 2000 12:16 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Model 2 and large applications
>
> Thanks for the response. I guess I should have been more clear. I'm not
> concerned about a performance impact. As you say, it should not be an issue.
> I *am* concerned about code complexity, manageability, and maintainability
> with as many forms as I have.
>
> --
> Martin Cooper
> Tumbleweed Communications
>
> ----- Original Message -----
> From: "Tim Fox" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, August 24, 2000 8:35 AM
> Subject: Re: Model 2 and large applications
>
> see below:
>
> Martin Cooper wrote:
>
> > I am currently looking at building a large application based on servlets
> and
> > JSP. The principles behind the Model 2 architecture are solid, and this
> > seems like the right approach. However, I have some concerns, and would
> like
> > to hear people's thoughts.
> >
> > The application I am building will likely comprise somewhere between 100
> and
> > 150 forms. The use of a single controller servlet, a la Model 2, is
> > attractive because it provides a focal point for security and database
> > connectivity, amongst other things. However, it raises some concern
> > regarding the manageability of so many "entry points" (for lack of a
> better
> > term).
> >
> > It seems that I would need some further structure to partition the
> > application. I have thought about creating "zones" of functionality, but
> > it's not clear (to me, at least) what the cleanest and most maintainable
> way
> > of doing this would involve.
> >
> > I have been looking at the Jakarta Struts framework, and very much like
> the
> > way that forms and actions are hooked up. However, I'm concerned that it
> > won't fly for an application with so many forms as I will have.
> >
> > By the way, this is an intranet app, not an Internet app, and, as such,
> > there will be a relatively small number of users. Scalability in number of
> > users is not important to me, but scalability in number of forms is.
>
> I don't see that using the model 2 type architecture will have any negative
> impact
> on the speed of your application.
> Just because all requests are being channelled through one servlet (the
> dispatcher)
> does not imply any any performance degradation compared to, say, calling the
> jsp
> files directly.
> This is assuming the dispatcher has been written correctly - the main thing
> to bear
> in mind is that your dispatcher must not be a thread bottleneck - this is
> ensured
> by not storing any state between requests in your dispatcher - ie everything
> should
> be on the stack.
>
> >
> >
> > Any thoughts would be very much appreciated.
> >
> > --
> > Martin Cooper
> > Tumbleweed Communications
> >
> >
> ===========================================================================
> > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> > Some relevant FAQs on JSP/Servlets can be found at:
> >
> > http://java.sun.com/products/jsp/faq.html
> > http://www.esperanto.org.nz/jsp/jspfaq.html
> > http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> > http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
> --
> Tim Fox (��o)
>
> Hyperlink interactive
> http://hyperlink.com
> email: [EMAIL PROTECTED]
> phone: +44 (0) 207 240 8121
>
> ===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
> ===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
> JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
>
> ===========================================================================
> To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
> Some relevant FAQs on JSP/Servlets can be found at:
>
> http://java.sun.com/products/jsp/faq.html
> http://www.esperanto.org.nz/jsp/jspfaq.html
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
> http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
