Darin Fisher <email@example.com>
December 19, 2001
The mozilla networking library, Necko, provides a full featured networking library, but it also carries with it some baggage. It is built using XPCOM (a simplified cross-platform component object model), and
- There is no way to use Necko without using XPCOM.
- Necko is not distributed as a stand alone library.
- Necko relies on other Mozilla components for supporting functionality (eg. preferences, cookies, ...).
- Necko must currently be compiled within the Mozilla framework.
- Necko requires a modern C++ compiler that, for example, has basic (ie. not necessarily complete) support for templates.
- Necko's API cannot be invoked from multiple application threads (you'll have to write code to marshall all necko calls to a single thread if you wish to use Necko in a multithreaded application).
- Necko's API is not frozen.
- Necko has many bugs (go to http://bugzilla.mozilla.org/ and query the Networking components ).
- Necko is well supported and ever evolving.
- Necko development is focused on performance and standards compliance.
- Necko uses NSS for HTTPS connections (note: Necko is not compiled against NSS... it uses PSM, which "plugs" itself into Necko).
- Necko is very customizable, powerful, and robust.
- Necko has gone through extensive field testing and revision to maximize website compatibility.
- Necko provides asynchronous DNS.
- Necko provides configurable disk and memory web caching.
- Necko provides support for web proxies, including PAC.
- Necko runs on many platforms.