W3C home > Mailing lists > Public > public-html@w3.org > November 2008

Re: Comments on HTML WG face to face meetings in France Oct 08

From: Geoffrey Sneddon <foolistbar@googlemail.com>
Date: Tue, 18 Nov 2008 22:09:48 +0000
Cc: elharo@metalab.unc.edu, Boris Zbarsky <bzbarsky@MIT.EDU>, Ian Hickson <ian@hixie.ch>, "Henry S. Thompson" <ht@inf.ed.ac.uk>, public-html <public-html@w3.org>, www-tag@w3.org
Message-Id: <90DE37C8-B768-4DCD-82B0-DD644FCD26D5@googlemail.com>
To: Henri Sivonen <hsivonen@iki.fi>


On 18 Nov 2008, at 21:33, Henri Sivonen wrote:

> The Validator.nu HTML Parser supports SAX in two different modes:  
> streaming and tree-buffered.
>
> In the streaming mode, the parser emits SAX events as it proceeds in  
> the input stream. However, there are some types of authoring errors  
> for which the error recovery is not streamable. These errors are  
> treated like XML well-formedness errors. I'd like to emphasize that  
> this behavior is conforming per spec:
> http://www.whatwg.org/specs/web-apps/current-work/#parse-error
>
> In the tree-bufferend mode, the parser builds a tree using a purpose- 
> optimized tree model (which is neither DOM nor XOM and outperforms  
> Xerces2 DOM and XOM for this use case) and after the input stream  
> has been exhausted, fires SAX events corresponding t

Would it not be possible to not just buffer when you reach something  
that cannot be said to certainly be the next event, or do you end up  
buffering the entire document in such cases?


--
Geoffrey Sneddon
<http://gsnedders.com/>
Received on Tuesday, 18 November 2008 22:10:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:24 GMT