There is nothing in Struts that really locks resources (threads, etc.), so
there wouldn't be any real scalability resources between coming in to one
servlet and coming in to multiple servlets.
> -----Original Message-----
> From: Sayles, Scott SAXONHQ [mailto:[EMAIL PROTECTED]]
> Sent: October 26, 2000 7:14 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: newbie question regarding performance
>
>
> Thanks for the feedback :)
>
> Unfortunately, I'm not familiar with implementing
> load-balancing techniques
> and we're probably not equipped to do anything like that anytime soon.
>
> I understand the higher level of control, convenience, etc.
> from using a
> servlet centric architecture. However, what I'm still
> wondering is if you
> have a high traffic site (whith a lot of requests to a single
> controlling
> servlet in an application) that is somewhat complex, based on
> the struts
> framework, would there be any greater benifit in utilizing
> multiple servlets
> (e.g. 2 controlling servlets for an application each with
> their own action
> mappings)? Yes, I know this defeats the purpose of the
> Struts framework,
> but I'm just exploring the idea. Would this reduce
> contention from the 1
> servlet architecture? Am I just being stupid?
>
>
> Thanks
>
> Scott
>
> -----Original Message-----
> From: McCay, Larry [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 26, 2000 6:09 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: newbie question regarding performance
>
>
> Scott,
>
> Scalability can be handled by the load-balancing techniques
> that you apply
> to your site. These mechanisms may be web farm configurations or
> application server deployment options.
>
> For example Bluestone Software's Total-e-Server (UBS) is
> typically deployed
> across multiple application hosts running multiple vm's. The
> Load Balance
> Broker (LBB) determines the optimal vm on the most
> appropriate application
> host to dispatch the request to.
>
> These types of approaches resolve high volume scalability
> before it actually
> reaches the web application itself.
>
> Having a single controlling servlet provides a single entry
> point to the
> application which becomes a convienient place to do many
> things that would
> otherwise be distributed accross your whole application - for
> instance form
> validation and repopulation of for elements in the event of
> input errors,
> authenticated a user, personalizing the application look and feel or
> collection of clickstream information.
>
> I hope this was helpful.
>
> Larry
>
> -----Original Message-----
> From: Sayles, Scott SAXONHQ [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, October 26, 2000 5:29 PM
> To: '[EMAIL PROTECTED]'
> Subject: newbie question regarding performance
>
>
>
> I'm relatively new to Struts and MVC based architecture for Web
> applications. What are the implications to using a single controlling
> servlet for a high volume site? i.e. do I have to worry
> about performace in
> regards to using a single ActionServlet for all our requests?
>
>
> Thanks
>
> Scott
>
