Also I will add that the last time I developed (part of ) an application like yours, the main performance barrier (in my environment at least) was not marshalling data across the network. It was by far multiple (often redundant) database accesses per user request. I would suggest you look into caching strategies somewhere in that middle layer.
Erik -----Original Message----- From: [EMAIL PROTECTED] Sent: Jul 20, 2005 3:25 PM To: Struts Users Mailing List <user@struts.apache.org> Subject: Re: Hi-New to this group http://java.sun.com/blueprints/corej2eepatterns/Patterns/SessionFacade.html Erik -----Original Message----- From: Maya menon <[EMAIL PROTECTED]> Sent: Jul 20, 2005 3:21 PM To: user@struts.apache.org Subject: Hi-New to this group Hi all, I am designing a web app/ Its supposed to have 500 concurrent users. 1. Module- Login The users login using their uid/password and see the stuff in their database I am planning to use Struts,jsp,action classes in the front end Now, back end I am thinking about session ejbs which reads database tables. The method for getting values from database tables will be implemented in a DAO. Now, what should I use in the middle layer ? ie, intercation between action classes and session ejb: For a struts based appp, whats best here ? Again 500 concurrent users. Thanks __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- 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]
