WebKit supports multipart/x-mixed-replace as long as the content type doesn't change (14149) or as long as it's not used through an XMLHttpRequest (14392):
http://bugs.webkit.org/show_bug.cgi?id=14149 http://bugs.webkit.org/show_bug.cgi?id=14392 The multipart/related (7168), multipart/mixed (9389) and multipart/alternate (no bug filed; please consider filing one) content types are not supported yet. http://bugs.webkit.org/show_bug.cgi?id=7168 http://bugs.webkit.org/show_bug.cgi?id=9389 I'm not sure the best way to implement support. At minimum you will need a MIME parser. I would take a look at how .webarchive files are loaded and mimic that. In theory, you shouldn't have to worry about the cache as long as all of the resources fit into memory. However, I think there may be an issue with subresources (such as CSS files) on the page not being cached properly for future reloads when coming from a webarchive (12605). http://bugs.webkit.org/show_bug.cgi?id=12605 Dave Sachin Puranik <[EMAIL PROTECTED]> wrote: > HI , > > As I checked there is no support for the multipart contents(multipart/mixed, > multipart/related, multipart/alternate) in the WebKit. What shall be ideal > way to extend this support. > > There are two approach in my mind. > > 1)parsing the content's other than HTML and Store as cached obkjects in > Cache manager. But if Cache is disable it will be a problem. > > 2)Deriving new class HTMLMultipartDocument from HTMLDocument /Document. > > Is there any other way to do it. > > Thanks and Regards > > Sachin _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
