[Bug 14884] New: Proposing a page including system

http://www.w3.org/Bugs/Public/show_bug.cgi?id=14884

           Summary: Proposing a page including system
           Product: HTML WG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: brunoaiss@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


You all should already know something called frames, don't you? What I'm
proposing here is something that will need some discussion and refining and
maybe you already thought about it and found problems with it but what I
believe that what I'm proposing here is useful for user bandwith, server
bandwith and specially, remove work from the server.
I'd like to see an HTML tag to include code from another page. This is not the
iframe tag. The iframe tag creates a browser inside a browser. I'm asking for a
complete inclusion of HTML code inside HTML code just like the include command
in PHP.
I believe that with this functionality we could have .html pages with dynamic
content without the need of AJAX.
Here's an example:
There's a page with a lot of content (a header, a footer, some images and ads)
and a table. The only thing that is dynamic is the table.
The server could host a user cacheable .html code with all the HTML and
Javascript for it to work and a small include for the table. The browser
executes an extra request for the table (just like it does for images, objects,
stylesheets...) and places that HTML substituting the include tag.
By doing this, by the next request to that page, the user can use the cached
version of the whole HTML + js + css except for the table, which will require
an extra request.

1 problem: How do the server knows if the browser supports the HTML include
system?
R: The answer relies in the headers. Among other headers, the browser would
send a header indicating that it is compatible with that system.
The server side language could then set header indicating that the browser is
allowed to cache the page (cache-control) and uses include tags. By doing this,
that page wont be needing any new visits from that browser for a while and only
the page with the table will need visiting.


Note: This idea needs refining and discussion. There are problems that really
need to be discussed before applying.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Sunday, 20 November 2011 10:02:45 UTC