View Single Post
Old 06-20-2009, 02:29 PM   #29
HarryT
eBook Enthusiast
HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.HarryT ought to be getting tired of karma fortunes by now.
 
HarryT's Avatar
 
Posts: 85,557
Karma: 93980341
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
Quote:
Originally Posted by netseeker View Post
No, that's just not true, kovid. You need just a basic knowledge about the parent tree of the element you are trying to render. That's a huge difference to "entire XHTML flows". Stream the xhtml, store the information about the parent tree that's really required into memory and "forget" the rest.
But wouldn't that imply that, in order to jump to any point in the file, you'd need to "stream" all the file content up to the point you're jumping to? That could be extremely slow, couldn't it? I think that's the whole point of parsing the file once and then storing the parse tree in memory, isn't it?

Last edited by HarryT; 06-20-2009 at 02:33 PM.
HarryT is offline   Reply With Quote