Frames are useless. So there is no use in complaining about them.
i have found them useful for one thing:
i write web applications with a lot of database interaction. frequently, i need to present a list of items from the database to the user, and the user then performs a number of operations on the items in that list. often, the query that generates the list of items is complex and expensive in terms of CPU cycles. by using frames, i can put the list in one frame and then the user can operate on the items in the list in the other frame. to achieve this without frames i'd either have to re-execute the query every time the user does something, or cache the list on the server, or pass the list back to the server in the POST operation and then pass it back to the client on the next page. by using frames, it just sits there on the client in its own frame without requiring any additional processing or caching.
if there were a way to achieve the same thing without frames i'd be glad to give them up.
Re:about frames...
Posted by: flacco on April 09, 2004 10:21 PMi have found them useful for one thing:
i write web applications with a lot of database interaction. frequently, i need to present a list of items from the database to the user, and the user then performs a number of operations on the items in that list. often, the query that generates the list of items is complex and expensive in terms of CPU cycles. by using frames, i can put the list in one frame and then the user can operate on the items in the list in the other frame. to achieve this without frames i'd either have to re-execute the query every time the user does something, or cache the list on the server, or pass the list back to the server in the POST operation and then pass it back to the client on the next page. by using frames, it just sits there on the client in its own frame without requiring any additional processing or caching.
if there were a way to achieve the same thing without frames i'd be glad to give them up.
#