Lauri, I'm still learning Struts myself, so I won't comment on its scalability or give an opinion of it. WebWork at OpenSymphony.com is an alternative MVC to consider.
Nick Faiz -----Original Message----- From: Lauri Jutila [mailto:[EMAIL PROTECTED] Sent: Wednesday, 29 October 2003 10:04 AM To: [EMAIL PROTECTED] Subject: Planning Struts Application Development Hello folks, I'm engaging in a web development project and my team is looking at Struts as a primary framework candidate for the application. Before we make final decision, I'd be glad to hear some commentary and experiences from real-world Struts users. Our project goal is to create an application which is leaning a little towards web-based group-ware applications in terms of feature set. No, we are not creating e-mail/calendar/task-list/foobar portal, but our app will include some of the basic group-ware app features and share quite many characteristics (different types of calendars come to mind). We would like our application to support at least hundreds of concurrent users. What kind of issues does this arise in terms of hardware and software/application configurations? How many users per app server would be feasible and how to handle multi-server environment gracefully? How is caching supported or implemented in Struts? What do you think are the fundamental issues to focus on design & development? And if you think, based on my very poor description of requirements, that Struts may not be the right framework, what are the alternatives? Best regards, -- Lauri Jutila [EMAIL PROTECTED] --------------------------------------------------------------------- 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]