Closed
Bug 77140
Opened 24 years ago
Closed 24 years ago
calls from java to xpcom and back should be thread transparent
Categories
(Core Graveyard :: Java to XPCOM Bridge, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: blackconnect, Assigned: blackconnect)
Details
Attachments
(1 file)
|
17.75 KB,
patch
|
Details | Diff | Splinter Review |
Here is a scenario.
Java object calls xpcom object method it calls some java object.
The last java execution should happen at the same thread the first invocation
occurs.
Threads switches when we call c++ xpcom object from java should be transparent
to java.
|
Assignee | |
Comment 1•24 years ago
|
||
moving to "Java to XPCOM Bridge"
Status: NEW → ASSIGNED
Component: Java-Implemented Plugins → Java to XPCOM Bridge
|
|
Assignee | |
Comment 3•24 years ago
|
||
|
|
Assignee | |
Comment 4•24 years ago
|
||
http://bugzilla.mozilla.org/showattachment.cgi?attach_id=32618 is a suggested
fix for the bug.
the logic schema is
in bcXPCOMStub::Dispatch push caller event queue in the callee thread local
storage.
at the time bcXPCOM proxy get called use stored event queue to execute call in
the right thread.
when bcXPCOMStub::Dispatch finished pop event queue from the storage.
NULL event queue means current thread.
I am closing this bug as fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
|
||
Updated•10 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•