Re:Frames for internal web applications (Score 1)

I have been doing some more research, and have answered the questions posed. As it turns out, the anti-frame dogma seems to be somewhat dated (due to improvements in the newer browsers) and apply mainly to the delivery of content (Internet-style surfing). The limitations of frames would actually seem to be advantages when developing APPLICATIONS to run on a Web server. Navigation needs to be restricted to the starting points of each application process. The Back button, Bookmarks, History, Printing, and valid URL's all represent problems to be solved in this context. Maintaining absolutely reliable state information and preventing people from jumping into the middle of a process are my biggest problems. The characteristics of frames that everyone hates so much are actually going to help solve some of them.