Isnt it the docshell/browser element calling asyncOpen from the channel
I return from my protocol handler? They are passing [xpconnect wrapped
nsIStreamListner] which I assume is the correct object. The funny thing
is when i removed a argument, it gave an error saying not enough
arguments for the onDataAvailiable function and when i alert the
listener.onDataAvailiable as a variable i get function() { native code
} or similar.Boris Zbarsky wrote: > James Newell wrote: > > I've got the error business sorted and I know what Async means just not > > how to implement it. What about onDataAvailiable, the doco for > > nsIStreamListner, the listener object passed to asyncOpen supposedly > > implements this function. > > Yes.... That's correct... Who's calling asyncOpen? What object are they > passing in as the nsIStreamListener? > > > I know that this code > > (http://www.mozdev.org/source/browse/archangel/src/archangel-protocol.js?rev=1.3&content-type=text/x-cvsweb-markup) > > isn't async but it supposedly works > > Fun. It's not guaranteed to work, and is allowed to crash given what they're > doing. And it's _definitely_ guaranteed to not work in some cases. > > -Boris _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
