Frames are the only option in some cases (eg when displaying embedded non-html documents). Bookmarking can be achieved by using a content "engine" which takes a page id and builds the frameset dynamically. I hate frames too, but they're a necessary evil sometimes :-/
Jim > -----Original Message----- > From: Reggie Burnett [mailto:[EMAIL PROTECTED]] > Sent: 18 April 2002 14:34 > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] To Frame or Not to Frame > > > I have always hated frames due to problems with bookmarking. > There has been > a steady tendency away from frames in general over the last 1-2 years. > > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]]On > Behalf Of > Rob Mc > Sent: Thursday, April 18, 2002 7:52 AM > To: [EMAIL PROTECTED] > Subject: [DOTNET] To Frame or Not to Frame > > > We are in the early design stages for an ASP.Net application > and are trying > to determine whether to use frames or an IBUYSPY type presentation > approach. We would very much appreciate any comments as to > the pros and > cons of either. > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe > from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
