3.2.1 - JRegistry in more detail

JRegistry class is actually quiet important, although most users will never have to deal with it.

The most common reason that anyone would have to use JRegistry is to change a protocol to protocol binding or adding a new user defined protocol.

To change a protocol binding, you would create a new instance of java interface JBinding and register it with JRegistry telling it which protocol is binding to which protocol. Then the scanner will know when to use your binding.

You can also register a completely new protocol. If have written a custom header definition, you can register that header with JRegistry which will remember it and assign it a unique numerical ID. The scanner only works with these numerical ids, indexing and setting up lookup tables etc, all based on the protocol id. New custom protocols need to be registered every time the application starts. These setting are not persistent. You may get a different numerical ID for your protocol.