> Regarding the docs, I honestly *DO NOT* agree with others comments
> that the docs are bad. I'll bet the docs are actually good *BUT* the
> examples are useless simply because there is not a single *COMPLETE*
> example in the entire document. Thus the reader needs to know the
> answer in order to ask the question.
>
> IMHO, all Tucows needs to do is provide *COMPLETE* examples for the
> basic operations; register, renew, delete, transfer. From there I
> think I could easily hack all the other possibilites in a reasonable
> period of time.
>
> And *COMPLET* mean just that!
>
> 1) Present the message being made of the server, and provide it as a
> text file
>
> 2) Show all messages used for any interlocks, and provide as a text file
>
> 3) Provide the packets after encryption as files. Thus I have a an
> incremental baseline from which I can verify my code.
If that is possible at all.
Do you really think you should go that deep? I hope if OpenSRS will do
something like "full dump of TCP/IP packets of Blowfish encrypted
renewal message with domain lock", they will put in a separate PDF :-)
BTW, I use my own client, too - simply calling the API methods from my
Perl modules. I have first thought about using JSP and creating
everything, encryption, registration beans, etc., but... the smart
choice is to find the tool which you can work the fastest, IMHO.
- Cs.
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:33 EDT