Frames and IFrames are useful for simultaneously displaying the results (responses) of multiple HTTP requests in the same browser window. You can use Frames, IFrames, and popup windows in your applications.
However, please be aware of these technical issues:
Using Frames and IFrames in any .NET page complicates post-backs because each Frame's document contains a separate HTML Form.
Inter-frame interaction is possible on the client side using Javascript, but the .NET convention, which Iron Speed Designer follows, is to use server side code whenever possible.
Inter-frame interaction is not possible on the server side because:
HTTP requests from Frames are indistinguishable from regular Requests.
Frame Requests are processed individually, often sequentially (but possibly simultaneously), and in possibly arbitrary order.
Because of these limitations, using Frames and IFrames can affect the server side session history mechanism and cause buttons which redirect "Back" to behave in an undesired manner.
A Request from a given Frame can only affect another Frame by emitting Javascript within its own Response to effect client side interaction, and / or by server side caching (assuming the affected Request is processed after the affecting Request) and special code within both pages.
Customizing Web Page Layout and Style
Using and Modifying Style Sheets
Placing ASP.NET Directives in Layout Pages
Automatically Refresh Page on Periodic Basis
Capturing the Enter Key in Layout Pages