Hello all,
I'm looking for a way of intercepting access to chrome://* and
resource://* URIs in my XULRunner application. Specifically, whenever
XULRunner asks for access chrome://myapp/ or resource://myapp/, I want to
be able to supply my own stream that may come from somewhere other than
the filesystem (my own in-memory data structure.)
My initial thought was to write protocol handlers but that doesn't seem
right. I'm now thinking maybe I need replace the default nsILocalFile
implementations with my own XPCOM components.
Can anyone offer any advice on the path-of-least-resistance?
- Edmond -
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
_______________________________________________
dev-tech-network mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-network
