Why is UrlConf needed at all?
Normally applications should register themselves for all protocols they understand. This works great for http:, https: (webbrowsers) and mailto: (MUAs). You can even configure which program should "own" a protocol if you have more than one.

Some programs don't bother registering for whatever reason. E.g., the makers of PuTTY refuse to register PuTTY as ssh: handler because there is no proper standard for ssh: URLs, yet. If you're like me and can't wait for that standard to be set in stone, then you could simply assume ssh: links will look a lot like telnet: links and use UrlConf to register PuTTY as ssh: protocol handler.

But what can you do with custom URL protocol handlers?
Personally I use it for an intranet web application that displays remote control links for hundreds of servers contained in its database.

How can URL protocol handlers be defined in Windows' Registry?
MSDN explains it here: About Asynchronous Pluggable Protocols, Registering an Application to a URL Protocol.

Last edited Aug 2, 2006 at 5:13 PM by rscharfe, version 1


No comments yet.