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.
Probably the first pointer that most people would give you is to be careful not to combine Business and Presentation logic. Bacically this means that you don't do everything in the same JSP since if the front end needs changing you have to re-write the Business logic as well and vice versa. As to how you efficiently separate these layers... Thats a bit of an argument... Dave.
Joined: May 03, 2001
Respected David O'Meara, Thank you very much for your reply I have seperated the presentation from logic Could you give some thing which i should be carefull about CODING
Improving the performance of a JSP application should use the same approach as improving the performance of any application. 1. Start by measuring the performance, in detail, to find out which parts of the process take longest. Addresss them first, when you have speeded up the slowest so that it is no longer the slowest, move on to the next slowest and improve that. 2. Keep an open mind. If the slowest part is the database (say), then optimize that, or if your webserver/JSP container is slow, consider reconfiguring/replacing that. 3. If the slowness is actually in the Java, apply the usual java speedups: make sure your code is doing only what it really needs to, re-use objects wherever possible rather than calling 'new' (especially very slow things like database connections or query results) and so on. Above all, find out what is slow before you start "optimizing", It will probably surprise you! If the problem is in the Java, consider asking some more detailed questions in the "performance" forum we have set up for just that purpose or consider buying Java Performance Tuning by Jack Shirazi.