Implement ServiceWorkerRegistration related DevTools events [1/2 blink]

Implement ServiceWorkerRegistration related DevTools events [1/2 blink]

This cl introduces the floowing events.
 - workerRegistrationUpdated
 - workerVersionUpdated
 - workerRegistrationDeleted

1/2 blink: https://codereview.chromium.org/984723003/
1/2 chromium: https://codereview.chromium.org/985663002/


BUG=463892
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=191596

[pfeldman, 2015-03-06 10:43:16]

pfeldman@chromium.org changed reviewers:
+ pfeldman@chromium.org

[pfeldman, 2015-03-06 10:43:16]

https://codereview.chromium.org/984723003/diff/1/Source/devtools/protocol.json
File Source/devtools/protocol.json (right):

https://codereview.chromium.org/984723003/diff/1/Source/devtools/protocol.jso...
Source/devtools/protocol.json:4116: { "name": "origin", "type": "string",
"description": "Security origin of requesting ServiceWorker registrations." }
What origin would we use?

I am not sure the pull model here is the way to go. In order to attach to the
workers, we'll need updates to be pushed. So I think what needs to happen is
upon "enable", all the registrations (or service workers) are sent to the
front-end along with their metainfo. Something like
workerRegistrationUpdated(registration). Then, as they change, updates will be
issued. Wdyt?

[horo, 2015-03-09 12:33:25]

https://codereview.chromium.org/984723003/diff/1/Source/devtools/protocol.json
File Source/devtools/protocol.json (right):

https://codereview.chromium.org/984723003/diff/1/Source/devtools/protocol.jso...
Source/devtools/protocol.json:4116: { "name": "origin", "type": "string",
"description": "Security origin of requesting ServiceWorker registrations." }
On 2015/03/06 10:43:16, pfeldman wrote:
> What origin would we use?
> 
> I am not sure the pull model here is the way to go. In order to attach to the
> workers, we'll need updates to be pushed. So I think what needs to happen is
> upon "enable", all the registrations (or service workers) are sent to the
> front-end along with their metainfo. Something like
> workerRegistrationUpdated(registration). Then, as they change, updates will be
> issued. Wdyt?

Ah yes, I agree with you.

I changed to push model.

[pfeldman, 2015-03-09 19:05:42]

lgtm

[horo, 2015-03-10 00:21:06]

The CQ bit was checked by horo@chromium.org

[commit-bot: I haz the power, 2015-03-10 00:22:56]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/984723003/20001

[commit-bot: I haz the power, 2015-03-10 01:54:59]

Committed patchset #2 (id:20001) as
https://src.chromium.org/viewvc/blink?view=rev&revision=191596