<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>I think there is still little clarity around the appcache behavior (dimich: are you bring over your "shadow frame" concept to webkit?).</div>
</blockquote><div><br></div></div><div>I'm wondering about bringing the 'shadow frame' technique to webcore too?</div></div></blockquote></div><br>If needs be :-) <br><br>Just to explain what is meant by 'shadow frame'
(I'm not sure it was discussed in webkit-dev beore): to provide access
to FrameLoader in Chrome's Worker process (which loads WebKit but
doesn't load any html, just creates a worker out of JS string), we
create a WebView and load it from a (url, encoding, mimtype, data)
source with empty data and the worker's url. This creates a frame with
a an empty document but with a right origin and encoding. This makes it
possible to create a ThreadableLoader (and underlying
DocumentThreadableLoader) w/o aceess to the original worker's parent.
This loader is used to implement XHR and importScripts in Chrome
workers. Oriinally a Darin Fisher's idea, it was implemented as
alternative to rollign out a new frame-less loader.<br>
<br>Shared workers can use the same approach since they can not forever hold the ref to the 'creating' document.<br><br>Dmitry<br>