--- The Forwarded Message Follows ---
--- Begin Message ---
On Wed, 15 Jan 2003 11:22:02 -0500
Colin Viebrock <[EMAIL PROTECTED]> wrote:
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.
If *COMPLETE* examples are really provided than why have
so many emails I've receive agreed with my position?
The API docs *ARE* wanting, and it is debatable as to what
should be done to fix them up.
2) Show all messages used for any interlocks, and
provide as a text file
I don't know what you mean by this.
Sorry, I was refering to examplifying all the required
"layers", and clearly teasing out each layer and show how
the layers depend on each other.
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.
You are paraniod. ;-)
What's absurbed about providing a completely detailed
baseline?
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 don't recall *EVER* requesting or expecting a Tucows
reseller provide me this information.
I do request and expect that *TUCOWS* provide *ALL OF US*
this information for a "throw-away key" that is dedicated
to the detailed documenation.
I for one don't buy it.
You are obviously far more inteligent than I am .....
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".
Thanks! A really do appreciate it!
--- End Message ---
