Can we stop exposing the socket transport service's nsIEventTarget outside of Necko?
- Kyle On Thu, Mar 26, 2015 at 8:14 AM, Patrick McManus <mcma...@ducksong.com> wrote: > good catch.. looking at > https://mxr.mozilla.org/mozilla-central/ident?i=NS_SOCKETTRANSPORTSERVICE_CONTRACTID > the only uses I see other than the one Ehsan unearthed are expected.. so > maybe that's the sum of the short term work. > > On Thu, Mar 26, 2015 at 10:06 AM, Ehsan Akhgari <ehsan.akhg...@gmail.com> > wrote: > >> On 2015-03-26 11:00 AM, Kyle Huey wrote: >> >>> On Thu, Mar 26, 2015 at 7:49 AM, Patrick McManus <mcma...@ducksong.com> >>> wrote: >>> >>> Is this thread mostly just confusion from these things sounding so much >>>> alike? Or am I confused now? >>>> >>>> >>> Most likely. >>> >>> Does anyone have actual data to show that this is a problem? >>> >> >> There's some truth to it. Looks like some code uses the *socket* >> transport service when it probably means *stream* transport service. >> Example: <http://mxr.mozilla.org/mozilla-central/source/dom/ >> workers/ServiceWorkerEvents.cpp#249> >> >> But other examples such as DOM Cache are not affected as far as I can >> tell. >> >> > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
