HTML
  Home arrow HTML arrow Remote Scripting with iframes
Dev Articles Forums 
ADO.NET  
Apache  
ASP  
ASP.NET  
C#  
C++  
ColdFusion  
COM/COM+  
Delphi-Kylix  
Design Usability  
Development Cycles  
DHTML  
Embedded Tools  
Flash  
Graphic Design  
HTML  
IIS  
Interviews  
Java  
JavaScript  
MySQL  
Oracle  
Photoshop  
PHP  
Reviews  
Ruby-on-Rails  
SQL  
SQL Server  
Style Sheets  
VB.Net  
Visual Basic  
Web Authoring  
Web Services  
Web Standards  
XML  
Mobile Linux 
App Generation ROI 
IBM® developerWorks 
Weekly Newsletter
 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid 
Request Media Kit
Contact Us 
Site Map 
Privacy Policy 
Support 
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
HTML

Remote Scripting with iframes
By: John Best
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: 5 stars5 stars5 stars5 stars5 stars / 3
    2008-12-22

    Table of Contents:
  • Remote Scripting with iframes
  • Using iframes for Site Navigation
  • Passing Data from Parent Window to iframe using Query String
  • Other uses

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      Del.ici.ous Digg
      Blink Simpy
      Google Spurl
      Y! MyWeb Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article
     
     
    ADVERTISEMENT


    Remote Scripting with iframes


    (Page 1 of 4 )

    In this second part of a two-part series on the ins and outs of iframes, we will explore more uses for iframes. The ones we will discuss fall into the broad category of remote scripting, or remote procedure calls (RPC). You won't find any sophisticated code in this article, but we will do quite a bit with just plain HTML tags and some basic PHP.

    What is remote scripting?

    To understand remote scripting, we should first consider how traditional web pages without remote scripting communicate with each other. When you click a link or submit a form on the first page, the second, also known as the "target page" to which the link or form points, loads into the browser, entirely replacing the first page. You see this process as your browser reloads. It takes some amount of time -- a small amount, granted, but enough to make some people impatient.

    With remote scripting, the first page remains loaded in the browser while it sends information to the target page. The target page then returns a response to the first page, which causes a dynamic change while the page remains loaded. In other words, a web page communicates with another web page or script by sending or receiving data or both, while the page is still loaded in the browser.

    If this is confusing to you, do not worry. It will become clear as we talk about some examples.

    More HTML Articles
    More By John Best


     

    HTML ARTICLES

    - Comparing Browser Response to Active Client ...
    - Testing Browser Response to Active Client Pa...
    - Active Client Pages: Completing the Code for...
    - ACP and Browsers: Setting up an Example
    - How Browsers Respond to Active Client Pages
    - Completing a Tree with Active Client Pages
    - HTML Form Verification and ACP
    - Building an ACP Tree
    - Completing an ACP 3D HTML Table Image Gallery
    - Building an ACP 3D HTML Table Image Gallery
    - A Multiple Page Image Gallery with Active Cl...
    - Building an Image Gallery with Active Client...
    - Concluding a Menu for All Browsers
    - A Vertical Menu for All Browsers
    - Downloading Long HTML Pages with ACP







    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 2 Hosted by Hostway
    Stay green...Green IT