Closed
Bug 32093
Opened 25 years ago
Closed 25 years ago
nsIStringBundle needs to have threadsafe nsISupports interfaces
Categories
(SeaMonkey :: General, defect, P3)
SeaMonkey
General
Tracking
(Not tracked)
People
(Reporter: tonyr, Assigned: ftang)
Details
I have to use nsIStringBundle from a different thread. In order to create the
string bundle so I can then call it through a proxy object, the AddRef/Release/
QueryInterface methods need to be threadsafe. This is accomplished using the
NS_IMPL_THREADSAFE macros rather than the plain NS_IMPL macros. nsIStringBundle
itself does not need to be threadsafe since it is called via proxy. (I wasn't
100% sure who to assign this to so hopefully I got it right?)
*** This bug has been marked as a duplicate of 31790 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 2•25 years ago
|
||
moving from architecture product to Browser. Architecture product is going
away.
Component: Internationalization → Browser-General
Product: Architecture → Browser
Version: 5.0 → other
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•