Anant Narayanan wrote: > I assume this means something like what has been implemented in the > SeaMonkey finger extension.
Yeah, that's probably a reasonable place to start. > Does this mean I can display a small XUL file that shows some sort of > "loading" message > while the request is being processed, and then show the actual data > when it arrives? You could, sure. Just create a multipart/x-mixed-replaced document, have the first part be the XUL, pump it into the listener, then wait for the data from the server before creating the second part and sending it to the listener. I assume that you only really expect these URIs to be used in docshells (iframes, etc) and not as <img src> and the like? > Also, is asyncOpen() the only method I am expected to > implement for an nsIChannel? No, you'd need to implement all of nsIChannel and nsIRequest. nsFingerChannel might still be a good basis for this. It might be nice to put a JavaScriptification of it up on the developer.mozilla.org wiki as an example.... Would you be willing to at least kick that off, if you're trying to understand how to rewrite it in JavaScript anyway? -Boris _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
