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.
We are migrating a legacy web application to a J2EE solution. The old solution was implemented using frames. It's like this - a frame to display a list, when a particular item is selected, it loads other frames with the details of the item selected. When the details are updated, it triggers a refresh of the list frame. (Lot of inter-frame communication) We're discussing possible alternatives. I want to find out general/specific advantages/disadvantages of using frames with a Struts/JSP application. Thanks.
Sound strong? Maybe it is, but they cause more problems than they solve, and if you have access to JSPs or some other server-side-includes you don't need them. I'm going to list a bunch of pet peeves about frames without justifying them
frames can get confused with external links and open those pages in frames
frames don't save bandwidth if the page is designed to cache properly
frames can cause display problems and browser specific behaviour if you mix secure and non secure pages
frames take you back to the original page if you refresh the page
frames stop you from being able to effectively bookmark pages
frames may not be supported in all browsers
you want to include someone elses site in yours/have some pages provided externally
you want a common menu and you're lazy
you have bunch of images and you aren't aware that the browser will cache them and you don't want them loaded again.
you think they look cool
OK, so I'm biased and that didn't work as well as I'd hoped. I hope this helps you though Dave