Boris Zbarsky wrote:
> John J. Barton wrote:
>> stream = channel.open();
>
> For some channels this won't return until there is data to read from the
> stream, so in the case of, say, an HTTP channel this will indeed process
> events before returning.
>
> This has been the case ever since open() became supported for all
> built-in channels, though... So since 2003 or so. See
> http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/netwerk/base/public/nsNetUtil.h&rev=1.106&mark=570-571#559
>
>
>
> Not sure about changes, though. But the whole event system has changed,
> so depending on where events are coming from and what else is going on,
> you might get slightly different event sequencing.
>
> -Boris
>
Thanks Boris. I think my confusion comes from too much javascript.
Since open() is synchronous and js is single thread, in my mind the
browser env should wait for open() to return. When my traces showed
other activity I imagined changes where none exist.
John.
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
