Very protocol?whether familiar (such as http, mailto, ftp, and about) or less familiar (such as JavaScript, VBScript, Outlook, NNTP, news, snews, and so forth)?is implemented on Windows machines as an asynchronous pluggable protocol (APP). These protocols can plug directly into Windows’ existing protocol framework. The only common protocol not implemented as an APP (at least on my computer) is SMTP. You can call any of these protocols from any interface in Windows that allows protocol interaction, regardless of whether the interface is programmatic or graphical.
To prove it, go to the Run command on your Start button and write the following:
javascript: alert("hello world");This should initiate whichever application is associated with the JavaScript protocol on your system, probably Internet Explorer, and execute the script. This is the same principle involved in bookmarklets. A bookmarklet is defined as “a tiny program (a JavaScript application) contained in a bookmark (the URL is a “javascript:” URL) which can be saved and used the same way you use normal bookmarks.”
You can use the JavaScript protocol from other browsers such as Mozilla, as Mozilla does not start up Internet Explorer when someone writes the code above in its address bar. Mozilla will pass any APP that it does not handle natively to the proper system handler. As I showed above, you can even use the JavaScript protocol from the Run box under your Start menu.
| What You Need |
| Windows 98 or later with IE 4 or later, Wscript, Rebol/View, and a text editor. |
MSDN provides some good information about APPs, but be wary of what you read: You may come away with a misconception about what is required to achieve the most basic implementation of an APP under Windows. For example, one article implies that to write an APP one needs to implement certain interfaces, but APPs are actually very flexible. The basic implementation of an APP under Windows requires only that you make the proper entries in the registry for your protocol and that the handler for your protocol is a valid Windows .exe file. You can see an example at http://msdn.microsoft.com/library/default.asp?url=/workshop/networking/pluggable/overview/appendix_a.asp. The “note” protocol defined in that example opens Notepad, similar to the way the view-source:// protocol can be used to open the .htm source of an HTML file in Notepad. For example, try putting this in your browser: view-source:http://www.devx.com.
I doubt that Notepad implements iinternetprotocol or any related interfaces, as to do so it should be a COM implementation and found at the following registry address HKEY_CLASSES_ROOTPROTOCOLS. Without these related interfaces, in the end all that happens is the protocol address is passed as a string via the command line to your application for analysis.
The W3C provides an incomplete list of addressing schemes, which you can use to search your system to see if these addressing schemes are implemented as APPs. Those that do more than just call over the command line should be found at the HKEY_CLASSES_ROOTPROTOCOLSHandler registry key.
There are many tools that allow you to dynamically load files via the command line, and pass on command lines to files. One example is script interpreters such as Wscript.exe. Here is the sample registry file, which shows how to set a simple WScript as the handler for a protocol called ws-proto.
Windows Registry Editor Version 5.00[HKEY_CLASSES_ROOTws-proto]@=""URL: ws-proto Protocol"""URL Protocol"=""[HKEY_CLASSES_ROOTws-protoshell][HKEY_CLASSES_ROOTws-protoshellopen][HKEY_CLASSES_ROOTws-protoshellopencommand]@="wscript.exe c:\wsproto.js %1"Here is the protocol that handles the WScript. (Both the registry file and the protocol handler are available in the code download for this article?see left column).
WScript.Echo(WScript.Arguments(0)); | |
| Figure 1: Howdy. As you can see the first command line argument passed on to our Wscript is everything you wrote in your address bar. |
To test this handler you can either make a new text file called settings.reg, copy the registry settings there, and then click to add the settings to the registry or use the settings.reg file in the code download. You should save the protocol handler code in c: in a file called wsproto.js. Once you’ve done this you can interact with the protocol in the same way you would with any other protocol. As an example, open your preferred browser and write the following: ws-proto://howdy. The result are shown in Figure 1. A JavaScript Alternative: Rebol
Most protocol implementations are done with a particular goal in mind, however there are certain protocols, such as the JavaScript protocol, that are designed to extend the functionality of the system as a whole, and the browser in particular.
It is this latter type that I will build in this article, using the JavaScript protocol as a model. The JavaScript protocol allows you to transmit JavaScript code that will then be evaluated within the browser. This means that the objects available to the protocol are the objects exposed by the browser. In our earlier example, the alert() functioned because alert() is supported in the browser environment.
 | |
| Figure 2: Security Check. Rebol’s default security asks you before it opens a port to our protocol interpreting script. |
I’m willing to bet there are a lot of folks out there, like me, who like scripting languages but abhor JavaScript. Using the same technique of dynamically loading a script in an .exe, as shown in the ws-proto example, it should be possible to make a protocol handler that accepts script in your favorite scripting language and evaluates it. This opens up the possibility of bookmarklets written in languages such as Python and Perl, as well as the usual VBScript and JavaScript. In the next part of the article I will make a protocol handler that accepts script in my favorite scripting language, Rebol.
Why Rebol? Because Rebol is particularly good at handling protocols. By implementing a dynamic evaluating protocol in Rebol, I can very easily add functionality to interact with ftp, smtp, http, etc. (These protocols are easily accessible from Rebol using Rebol’s one-liner scripts, e.g. one line of code to read a URL and write the output to a local file.) Rebol can interact with any protocol that can be called via bookmarklet-type behavior, from a link on a web page, from writing in the address bar, from shortcuts, or from most any programming language/environment in the Windows system.
 | |
| Figure 3: Rebol View. The large text area contains the URL body you passed by clicking on the link. |
You can download a free, noncommercial version of Rebol from http://www.rebol.com/downloads/view-pro031.zip. It includes a Rebol dialect (sort of a DSL) for graphical interfaces, which I will use to implement a small form in my script. This form will help me decide, by showing the code passed to it, whether to evaluate the code, append it to a local file containing the script fragments I receive, or to edit it and then evaluate it.
It’s time to implement the Rebol script. There are links at various points to the Rebol function dictionary, which provides definitions of built-in Rebol functions to help you along. In the code download for this article there is a registry file called rebsettings.reg, which sets the reb protocol to be evaluated using a script called reb.r. Reb.r is the protocol handler that the registry files point at (see Listing 1). Install Rebol in the default installation folder c:
ebolview. Be advised that the Rebol installation program asks you for information such as your email address, email server etc., which it needs to send and receive mail and for the examples to work.
Once Rebol is installed, you should merge the accompanying .reg file and also install the files in the downloadable sample code (see link in left column) to the c:
ebolview directory. When you’ve done that, open the example.html file in your default browser. Listing 2 shows the contents of the example.html file.
This file has three simple JavaScript functions called callreb(),browseloc(), and insertPrompt().
- Callreb() takes a string parameter, which should be a reb:// link, and then uses the browser’s location.href method to navigate to the reb:// link.
- When executed in a link, browseloc() will tell Rebol to browse the page on which the link was executed.
- The insertPrompt() function accepts three arguments and builds a string containing the reb:// protocol. The middle argument is the result of a JavaScript prompt that gets a user-entered value and places it in the middle of the reb:// protocol.
The first link in the HTML page is:
read a local file and write result to new local fileEverything past the reb:// is legal Rebol code. And it does exactly what the link text tells you: It reads a local file, contained in the code download called oldfile.txt and writes a local file called newfile.txt. (Note that the parameters are intentionally opposite their function?this is because of the evaluation order of Rebol syntax). The % before the file names tells Rebol that these are in fact files. When you click on the link you should see something similar to Figure 2:
The popup is generated by Rebol’s built-in security (more information on controlling Rebol security settings). When you click Yes, reb.r loads (see Figure 3).
Pressing Do causes the Rebol interpreter to evaluate the text contained in the
