Closed Bug 599970 Opened 14 years ago Closed 14 years ago

Add GetInterface for nsIEventTarget on Connection

Categories

(Core :: SQLite and Embedded Database Bindings, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla2.0b9

People

(Reporter: sdwilsh, Assigned: sdwilsh)

References

Details

(Whiteboard: [fixed-in-places])

Attachments

(1 file)

It could be useful for consumers to post an event to the async thread. However, this would be a *highly* advanced operation that most consumers wouldn't need, so we should make Connection implement nsIInterfaceRequester, and when it is asked for an nsIEventTarget, go ahead a return the background thread.
Blocks: 599973
Patch I have needs to be applied on top of bug 596970 (not a typo, it is in fact 3000 less than this bug)
Depends on: 596970
Attached patch v1.0Splinter Review
BAM
Assignee: nobody → sdwilsh
Status: NEW → ASSIGNED
Attachment #481060 - Flags: review?(bugmail)
Whiteboard: [needs review asuth]
Comment on attachment 481060 [details] [diff] [review] v1.0 I presume "*highly* advanced operation" === "do not document this on the IDL; for use only by those proficient in precisely shooting between their toes"? I'm going to treat this as a warranty voiding operation. Specifically, this adds some potentially new situations where a reference can go out of scope on the async thread that are not already covered but I'm not going to look into those. That's on whomever writes the code that dispatches to the async thread...
Attachment #481060 - Flags: review?(bugmail) → review+
(In reply to comment #3) > I presume "*highly* advanced operation" === "do not document this on the IDL; > for use only by those proficient in precisely shooting between their toes"? Yup. > I'm going to treat this as a warranty voiding operation. Specifically, this > adds some potentially new situations where a reference can go out of scope on > the async thread that are not already covered but I'm not going to look into > those. That's on whomever writes the code that dispatches to the async > thread... Yeah, there were a few threadsafety things I thought about defending against, but then I realized that doing this means you damn well better know what you are doing or you will go boom somewhere anyway.
Whiteboard: [needs review asuth] → [has review]
Whiteboard: [has review] → [fixed-in-places]
Depends on: 602755
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.0b9
Product: Toolkit → Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: