>> And *COMPLET* mean just that! >> >> 1) Present the message being made of the server, and provide it as a >> text file
These are provided in the API spec. >> 2) Show all messages used for any interlocks, and provide as a text file I don't know what you mean by this. >> 3) Provide the packets after encryption as files. Thus I have a an >> incremental baseline from which I can verify my code. You want a TCP dump of the encrypted data? That is simply absurd. First, the paranoid among us will think you are going to try and reverse-hack our encryption keys. Second, if you honestly claim to be able to understand Blowfish encrypted TCP packets, but can't understand the OpenSRS API specifications ... well ... I for one don't buy it. I'm sending to you, not cc'ing the list, the XML dump of a domain lookup (generated using the PHP class, but that's irrelevant). That, plus some reading of the API specs, should be more than enough for you to get started ... especially if you've been "programming micro compunters since [you] purchased a TRS-80 back in 1976". - Colin
