On Tuesday 04 December 2012, Adam Barth wrote: > There's been a somewhat fragmented discussion across webkit-dev and > various bugs about how we ought to approach multiprocess networking in > WebKit. In an attempt to organize my thoughts, I wrote up a short > design document that compares various approaches: > > https://docs.google.com/document/d/1ihpwbiG_EDirnLibkkglEtyFoEEcf7t9XNAn8JD > 4fQY/edit > > My hope is that this document will be useful as a starting point for > discussion. If other folks have written similar documents, those > might make valuable contributions to the discussion as well. > > I welcome your feedback, either via comments in the document or via > this email thread. > I like your ideas, but at least the two first points are in my mind operating system tasks, and already handled by some WebKit backends, so I hope it will be possible to put this logic at as high level as possible making it easier to ignore where it is unnecessary. I am considering it operating system tasks, because the benefits WebCore processes has in sharing connections or cache is the same all applications on a platform would have in doing the same.
About the network process, I would just like to suggest not limiting it to one, not even to begin with. There is not much simplicity or efficiency to be gained by keeping all network request in the same process, and extra processes could be used for faster responses and increased security. Regards `Allan Sandfeld _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev