dom/media has a very useful system called SharedThreadPool that gives you
static on-demand access to a named (and refcounted) threadpool. Probably
just moving that to XPCOM and then coming up with a naming convention
("MiscThreadPool" or something) might solve this problem.On Thu, Mar 26, 2015 at 8:37 AM, Randell Jesup <[email protected]> wrote: > >Can we stop exposing the socket transport service's nsIEventTarget outside > >of Necko? > > If we move media/mtransport to necko... or make an exception for it (and > dom/network/UDPSocket and TCPSocket, etc). Things that remove loaded > footguns (or at least lock them down) are good. > > Glad the major real problem was too-similar-names (I'd never heard of > STREAMTRANSPORTSERVICE (or if I had, it had been long-forgotten, or > mis-read as SOCKETTRANSPORTSERVICE)). > > -- > Randell Jesup, Mozilla Corp > remove "news" for personal email > _______________________________________________ > dev-platform mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
