Dev : Protocol Handlers: Difference between revisions
From MozillaZine Knowledge Base
Jump to navigationJump to search
No edit summary |
|||
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
All URIs and URLs start with a specific scheme such as HTTP or FTP. Mozilla uses XPCOM components to implement protocol handlers for each type of scheme it supports. These components can be written in C/C++ or JavaScript. | All URIs and URLs start with a specific scheme such as HTTP or FTP. Mozilla uses XPCOM components to implement protocol handlers for each type of scheme it supports. These components can be written in C/C++ or JavaScript. | ||
== | ==Documentation== | ||
* [http://www.nexgenmedia.net/docs/protocol/ Adding a New Protocol to Mozilla] | * [http://www.nexgenmedia.net/docs/protocol/ Adding a New Protocol to Mozilla] | ||
* [http://www.mozilla.org/developer/ Mozilla.org - Writing A Mozilla Protocol Handler] | |||
* [http://www.mozilla.org/projects/netlib/necko_url.html Mozilla.org - URIs and URLs] | |||
* [http://lxr.mozilla.org/seamonkey/source/netwerk/base/public/nsIProtocolHandler.idl LXR page for nsIProtocolHandler interface] | |||
==Protocol Handlers== | |||
* [http://lxr.mozilla.org/seamonkey/source/extensions/finger/ Mozilla.org - Finger Protocol Handler] | |||
* [[Dev : Extending the Chrome Protocol | Extend the Chrome Protocol Handler]] | |||
[[Category:Development]] | |||
Latest revision as of 02:26, 16 April 2005
All URIs and URLs start with a specific scheme such as HTTP or FTP. Mozilla uses XPCOM components to implement protocol handlers for each type of scheme it supports. These components can be written in C/C++ or JavaScript.
Documentation
- Adding a New Protocol to Mozilla
- Mozilla.org - Writing A Mozilla Protocol Handler
- Mozilla.org - URIs and URLs
- LXR page for nsIProtocolHandler interface
