983928 - Make protocol.js usable from content privileged code

Status: RESOLVED FIXED

(Add-on SDK Graveyard :: General, defect, P1)

Description

[Irakli Gozalishvili [:irakli] [:gozala] [@gozala]]

Given that add-on pages don't have chrome privileges it would make a lot of sense
to make version of protocol.js that can be loaded in a content page & given a [MessagePort](http://www.w3.org/TR/webmessaging/#messageport) representing remote debugging protocol connection to a debuggee it should be able to generate high level OOP style API that could be used by add-on's.

Comment 1

[Irakli Gozalishvili [:irakli] [:gozala] [@gozala]]

In order to generate high level APIs dynamically from a raw connection we would need a way for actors
to describe themselves. My understanding is that Bug 983331 does exactly that.

Comment 2

[Irakli Gozalishvili [:irakli] [:gozala] [@gozala]]

Attachment: Client side extraction from protocol.js

Comment 3

[Dave Camp (:dcamp)]

Comment on attachment 8418225 [details] [review]
Client side extraction from protocol.js

Let's get this landed so we can iterate.