Closed
Bug 758270
Opened 12 years ago
Closed 12 years ago
Electrolysize Permission Manager
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
blocking-basecamp | + |
People
(Reporter: jstraus, Assigned: jstraus)
References
Details
Attachments
(1 file)
9.66 KB,
patch
|
Details | Diff | Splinter Review |
Permission Manager needs to support multiple processes for B2G. Create multi-process for Permission Manager. Child processes could subscribe to changes and cache results for quick answers when the decision is already made.
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → jstraus
Assignee | ||
Comment 1•12 years ago
|
||
Here is an ipdl for the electrolization of PermissionManager. It isn't clear how the multi-process Gecko is going to work. I'm not sure how this communication will be set up, as I expect there will be several ipdls needing to communicate to the children content processes. Also, I don't think the WebAPI versions of testPermission will need to be available to the children content processes (as I don't expect the APIs to live in the children content processes). I can eliminate them from the interface once it is known. I did include a notification of changes so that the children versions can cache results for quicker answers. Until there is more infrastructure in place, I can't assess the security implications.
Updated•12 years ago
|
blocking-basecamp: --- → ?
Isn't this already working? How could we have shipped XUL-Fennec which was multi-process if the permission manager wasn't working in child processes? Blocking on figuring this out either way though.
blocking-basecamp: ? → +
Comment 3•12 years ago
|
||
Yes, nsPermissionManager fully supports multiple content processes.
Jim: should this be marked as WORKSFORME then? Or did you have any additions in mind?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•