Closed
Bug 289227
Opened 19 years ago
Closed 18 years ago
XPCOM proxies should only require nsIEventTarget to indicate destination thread
Categories
(Core :: XPCOM, enhancement, P5)
Core
XPCOM
Tracking
()
VERIFIED
FIXED
mozilla1.9alpha1
People
(Reporter: darin.moz, Assigned: darin.moz)
References
Details
(Keywords: arch)
Attachments
(1 file)
|
35.27 KB,
patch
|
Details | Diff | Splinter Review |
XPCOM proxies should only require nsIEventTarget to indicate destination thread nsIEventTarget provides PostEvent and IsOnCurrentThread, which appears to be all we need.
|
Assignee | |
Updated•19 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P5
Target Milestone: --- → mozilla1.8beta2
|
|
Assignee | |
Comment 1•19 years ago
|
||
My patch in bug 287648 provides motivation for this bug.
|
|
Assignee | |
Comment 2•19 years ago
|
||
A couple issues to consider: 1) The current API supports NS_CURRENT_EVENTQ and NS_UI_THREAD_EVENTQ as valid event queues. Those are of type nsIEventQueue and not nsIEventTarget, so we would need to resolve that somehow. There is no notion yet of current thread event target, though I would like to invent such a thing. 2) The implementation uses PostSynchronousEvent, which is not exposed on nsIEventTarget. We would need to either implement that ourselves or modify nsIEventTarget to expose it.
|
|
Assignee | |
Comment 3•19 years ago
|
||
|
|
Assignee | |
Updated•19 years ago
|
Target Milestone: mozilla1.8beta2 → mozilla1.9alpha
|
|
Assignee | |
Updated•18 years ago
|
Depends on: nsIThreadManager
|
||
Updated•18 years ago
|
QA Contact: xpcom
|
||
Comment 4•18 years ago
|
||
seems to have been fixed by bug 326273
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•