[Webkit-unassigned] [Bug 51364] Web Inspector: Remote Web Inspector - Cross Platform InspectorServer

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon May 23 11:27:34 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=51364





--- Comment #62 from Joseph Pecoraro <joepeck at webkit.org>  2011-05-23 11:27:33 PST ---
(In reply to comment #60)
> Can we split this off into multiple bugs?  This bug hasn't been touched in over
> a month and it's unclear what if anything needs to be done here.

If this gets readdressed in the future it can be split into multiple bugs.

Most of the earlier patches would still be valid, but its useless landing
them without them being used by the later patches. They would just be
dead code.

To clarify what could be done, Pavel raised some concerns that in a
multiprocess model page discovery cannot be handled in WebCore
like "New Part 5" tried to do. That is a valid concern for Chromium
and probably WebKit2 as well. So, handling page discovery could be
moved into the WebKit client layer. Here was his comment:

(In reply to comment #50)
> (From update of attachment 80254 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=80254&action=review
> 
> My biggest concern is that this class lives in the WebCore. In Chromium, we can't do
> page discovery from within the WebCore and we also can't open listen socket from
> there. What is it going to be like in WebKit2? I was thinking that we implement it a bit differently:
> - WebCore (or WebKit/cf) contains code that can be reused by the platforms in order to support HTTP/WebSocket server infrastructure
> - WebKit layer instantiates it and pipes messages to the corresponding InspectorController instance.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list