ISSUE-56: Section 3.6: examples of activities which are computationally intensive
Section 3.6: examples of activities which are computationally intensive
- State:
- CLOSED
- Product:
- Best Practices Document
- Raised by:
- Philipp Hoschka
- Opened on:
- 2005-11-10
- Description:
- [updating previous suggested issue]
Issue
-------
Would be nice to have examples what activities are computationally
intensive - this could help content providers to avoid them, if
possible, and potentially lead to more BPs
> Some activities associated with rendering web pages are computationally
intensive.
One of the things that have been mentioned in a paper presented at the
MWI workshop in Barcelona was actually invalid markup, so maybe that\'s a
good example
http://www.w3.org/2004/10/MWIWS-papers/W3C_Mobile_Web_Initiative_-_T-Mobile_Position_Statement-final.pdf
> The very fact that advanced browsers allow greater mark-up flexibility
unfortunately reduced the amount of care taken to assure standards compliance
and led to a broader use of sloppy mark-up – but unlike to desktop browsing this
has quite severe consequences for users of devices with radically limited
resources: rendering non-deterministic mark-up has a very real impact on CPU,
memory and battery life, and also mostly leads to unwanted and costly data
overhead on the radio transmission – for customers and operators all alike.
Suggested rewrite
------------------
Some activities associated with rendering web pages (e.g. parsing and
displaying invalid markup) are computationally intensive.
- Related Actions Items:
- No related actions
- Related emails:
- RE: [minutes] Thursday Dec 1 teleconference (from paul.walsh@segalamtest.com on 2005-12-02)
- [minutes] Thursday Dec 1 teleconference (from dom@w3.org on 2005-12-01)
- [minutes] Thursday Dec 1 teleconference (from dom@w3.org on 2005-12-01)
- New BP Draft 1k (from jo@linguafranca.org on 2005-11-28)
- ISSUE-56: Section 3.6: examples of activities which are computationally intensive (from dean+cgi@w3.org on 2005-11-10)
Related notes:
No additional notes.
Display change log
