View Single Post
Old 06-20-2009, 02:42 PM   #30
netseeker
sleepless reader
netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.
 
netseeker's Avatar
 
Posts: 4,763
Karma: 615547
Join Date: Jan 2008
Location: Germany, near Stuttgart
Device: Sony PRS-505, PB 360° & 302, nook wi-fi, Kindle 3
Quote:
Originally Posted by HarryT View Post
Are you suggesting that, if you wanted to jump to a point 9.9MB into a 10MB file, you'd need to "stream" all the preceding 9.9MB of the file in order to get the state data for the point you're jumping to? That sounds horribly time consuming. I think that's the whole point of parsing the file once and then storing the parse tree in memory, isn't it?
You just need segments of the parse tree in memory to apply the required styles. So you can overead large parts of the 9.9 MB. But yes, for more distant positions in a big file you would have to read/inspect large parts of the file (again). That's what some mobile browsers are doing. Look, mobile device these days have powerful CPUs and very fast I/O. It's just the way it works. You can't hold the complete parse tree in memory on all devices.
netseeker is offline   Reply With Quote