This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I think there is lot of memeory overhead using struts, because if you made lot of html tags using stuts html tags, each tags associted with the class... In large projects, some persons recommend that to use struts.But i think MVC pattern is not very difficult to implement. MVC is there to develop application neatly and quickly.
That doesn't really have anything to do with Struts, does it? It's about custom tags. Two things. First, it's not memory usage that's significant; after all, all those tags won't live any longer than it takes to render the JSP. My experience is that this is only a fraction of the total response time. Object churn might more be a problem, but modern JVMs do a good job of efficiently collecting short-lived objects. And in any case this is the JSP container's responsibility to worry about: containers are free to recycle JSP tag objects to some extent. Second, you can't be serious about wanting to avoid custom tags. That's not just saying "no" to Struts, it's also saying "no" to the JSTL, to JavaServer Faces, to just about everything that's nice and sexy about JSPs today - Peter [ June 27, 2003: Message edited by: Peter den Haan ]
Joined: Jun 09, 2003
thanks for reply.. Now suppose 1000 requests arrives at server, thousands of objects are created for handling these requests. In this senario what do you think about extensive usage of struts and other frame works like Cocoon etc. In this case, still there is no responsibility of develpor to see the memory managment and other issues or server can handel this?