it sounds like overbite is using it as intended.

On Fri, Apr 3, 2015 at 2:19 PM, Cameron Kaiser <ckai...@floodgap.com> wrote:

> On 3/26/15 8:37 AM, Randell Jesup 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)).
>>
>>
> The OverbiteFF (gopher and legacy protocols) add-on uses
> nsISocketTransportService to open sockets, and I'm sure it's not the only
> one that does. The implementation is non-blocking, but I want to clarify
> from the above post that the intention is not to block non-Necko consumers
> from using it. Is this acceptable usage, or is it deprecated?
>
> Cameron Kaiser
>
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to