Struts is the least of your teams performance concerns. It would do you good
service to simply take Struts as heling you organise servlets & jsp's and go
chasing bigger problems like persistence and selection of architecture & app
server. Struts doesn't change the Servlet model. It doesn't change the
approach to servlet threading. Servlets are singletons, so are Actions, for
all the same good reasons. Struts just helps you keep a tidy house on the
interface tier. Trust us when we say that all the stuff to worry about happens
out the back.
These bigger picture things are better asked to forums like...
http://www.theserverside.com
...you'll even get opinions of those using Struts to front large applications.
You can even get opinions down to the design pattern level. TheServerSide.com
itself runs on a cluster of app servers from four different vendors. I'm
pretty sure TheServerSide is exactly what you're looking for.
Arron.
> Hi,
>
> Has anybody successfully managed to use Struts in a distributed\clustered
> environment? If so with what setup? And did you have any Struts related
> difficulties?
>
> Thanks,
>
> Tin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
