W3C home > Mailing lists > Public > public-webarch-comments@w3.org > October to December 2004

Re: PR-webarch-20041105

From: Chris Lilley <chris@w3.org>
Date: Mon, 29 Nov 2004 17:15:34 +0100
Message-ID: <806877036.20041129171534@w3.org>
To: public-webarch-comments@w3.org
Cc: (wrong string) åkon Wium Lie <howcome@opera.com>

Hello public-webarch-comments,

Second draft, with Håkon's comments incorporated

  Note that when content, presentation, and interaction are separated by
  design, agents need to recombine them. There is a recombination
  spectrum, with "client does all" at one end and "server does all" at
  the other.

  There are advantages to each: sending device capabilities to the server
  (for example, using CC/PP) allows tailoring of the content to specific
  devices (such as mobile phones). For example links can be adjusted to
  point to lower resolution images, smaller video or no video at all,
  giving a faster download; if the content has been authored with
  multiple branches, the server can remove unused branches too. In
  addition a small amount of client side computation is saved. However,
  this makes the content more specific to a particular device, reducing
  caching efficiency.

  On the other hand, recombination on the client makes the delivered
  content applicable to a wider range of devices. This improves caching
  efficiency and gives users more presentation options. It can be
  tailored to particular groups of devices by using media specific style
  sheets. For textual content with a regular and repeating structure,
  the combined size of the text content plus the style sheet is
  typically less than that of a fully recombined content; the savings
  improve further if the style sheet is reused by other pages.

-- 
 Chris Lilley                    mailto:chris@w3.org
 Chair, W3C SVG Working Group
 Member, W3C Technical Architecture Group
Received on Monday, 29 November 2004 16:15:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 6 April 2009 12:37:33 GMT