[tw] innards of modern browsers?
Hi Folks, Since this is pretty central to TiddlyWiki, I figure someone here might be able to point me at documentation (presentation form would be nice) about the innards of modern browsers. I'm particularly looking for information about some of the newer HTML5 storage and webapp functionality - and even more specifically what gets stored, and how, if one edits the content of an active page via JavaScript - what state can be saved, and how does it happen (and which of this is dictated by standards vs. by specific browser designs). Thanks Very Much, Miles Fidelman -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Re: [tw] innards of modern browsers?
Hi Miles This is quite a good starting point for finding out more about how browsers work: http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/ I think though that your specific questions might be answered by the HTML 5 specs. Basically, all the storage features are exposed as JavaScript APIs, and things only get stored explicitly. So, if one edits the contents of an active page then nothing will get stored unless JS code explicitly does so. In terms of caching, the caching mechanisms in browsers are at the network level. So they cache the results of particular network requests, rather than caching the state of the document as it changes. Best wishes Jeremy -- Jeremy Ruston jeremy.rus...@gmail.com On 7 May 2012, at 16:11, Miles Fidelman wrote: > Hi Folks, > > Since this is pretty central to TiddlyWiki, I figure someone here might be > able to point me at documentation (presentation form would be nice) about the > innards of modern browsers. I'm particularly looking for information about > some of the newer HTML5 storage and webapp functionality - and even more > specifically what gets stored, and how, if one edits the content of an active > page via JavaScript - what state can be saved, and how does it happen (and > which of this is dictated by standards vs. by specific browser designs). > > Thanks Very Much, > > Miles Fidelman > > -- > In theory, there is no difference between theory and practice. > In practice, there is. Yogi Berra > > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To post to this group, send email to tiddlywiki@googlegroups.com. > To unsubscribe from this group, send email to > tiddlywiki+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/tiddlywiki?hl=en. > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
Re: [tw] innards of modern browsers?
Hi Jeremy, Thanks! And... Jeremy Ruston wrote: Hi Miles This is quite a good starting point for finding out more about how browsers work: http://www.html5rocks.com/en/tutorials/internals/howbrowserswork/ Unfortunately, it doesn't really talk about how JavaScript interacts with things. However.. it contains a list of references that point to: http://www.vineetgupta.com/2010/11/how-browsers-work-part-1-architecture/ which does, at least a little. I think though that your specific questions might be answered by the HTML 5 specs. Basically, all the storage features are exposed as JavaScript APIs, and things only get stored explicitly. So, if one edits the contents of an active page then nothing will get stored unless JS code explicitly does so. As far as I can tell, the HTML5 spec days very little about HTTP interactions. In terms of caching, the caching mechanisms in browsers are at the network level. So they cache the results of particular network requests, rather than caching the state of the document as it changes. Right... but think about things like HTTP PUT, POST, DELETE and interactions with AppCache. As far as I can tell, there is nothing in the HTML5 documents, or anywhere else, that talks about this. And it gets just that much trickier, when talking about executing a page headless, say with node.js. Sigh... Miles -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
