Closed
Bug 496468
Opened 16 years ago
Closed 16 years ago
electrolysis: First steps to running plug-ins in a separate process
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: cjones, Assigned: cjones)
Details
Attachments
(2 files, 1 obsolete file)
|
177.77 KB,
text/diff
|
Details | |
|
203.09 KB,
patch
|
Details | Diff | Splinter Review |
The "real" bug about plugin processes is bug 156493. This one is open to allow cjones and bent to track and backup their initial work.
| Assignee | ||
Comment 1•16 years ago
|
||
Loads plugin DSO in separate process, doesn't do much else. Lots of chromium lib cleanup. Next up is talking to the plugin.
| Assignee | ||
Updated•16 years ago
|
Attachment #381660 -
Attachment mime type: application/octet-stream → text/diff
| Assignee | ||
Comment 2•16 years ago
|
||
Differing approach from the first. Starting to sort out protocol vs. transport layer, attempt to own channel semantics. Posted purely for personal archival.
| Assignee | ||
Comment 3•16 years ago
|
||
Pushed about as far as I can get without an NPRuntime. The application/x-test plugin won't draw, and (apparently) flash as well, without that. Numerous hacks abound, so a "personal archival purposes" disclaimer still applies.
Attachment #382461 -
Attachment is obsolete: true
Comment 4•16 years ago
|
||
any updates to add on this?
Comment 5•16 years ago
|
||
fixed in electrolysis
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•