W3C home > Mailing lists > Public > www-html@w3.org > August 1998

RE: OBJECT, inheritance, and rendering

From: Walter Ian Kaye <walter@natural-innovations.com>
Date: Tue, 4 Aug 1998 16:29:40 -0700
Message-Id: <v0313030bb1ed3f22de6d@[134.79.129.61]>
To: www-html@w3.org
At 2:52p -0700 08/04/98, Todd Fahrner wrote:
>
>would be comparable to a server-side include. Even better, perhaps: be able
>to include id's within complete HTML documents; e.g.,
>
><OBJECT data="http://www.prismaticbooger.com/index.html#chug"
>type="text/htmf">
>   <em>Unfortunately, your UA doesn't support OBJECT for inclusion of HTML
>   fragments, so you're reading this instead.</em>
></OBJECT>
>
>This would render the element whose id="chug" and all its children, exactly
>as if the element had been included server-side, with all the usual
>inheritance rules applying.
>
>Servers could pre-process such files as they were being served in order to
>take care of legacy UAs, or just to speed things along as load permitted.
>UAs could fetch their own includes if bandwidth were high, or let the
>server do it if low.

Umm, could someone explain the advantage of a CSI over a SSI?
I cannot think of a single application for a client-side include.
Don't most servers do SSIs these days? And by the time browsers
all support CSIs (if that would ever happen), wouldn't all servers
be doing SSIs? And if so, why not just use SSIs?
Received on Tuesday, 4 August 1998 19:31:02 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:37 GMT