Let me try to put my situation into a different
perspective:
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.
4) etc.
Again, I don't need many examples. But I absolutely need
at least one baseline from which to work!
OK, I'm done venting ......
- Re: OpenSRS API Question bill
- Re: OpenSRS API Question Lynn W. Taylor
- Re: OpenSRS API Question inbox
- RE: OpenSRS API Question inbox
- Re: OpenSRS API Question Lynn W. Taylor
- Re: OpenSRS API Question bill
- Re: OpenSRS API Question inbox
- Fwd: OpenSRS API Question inbox
- Fwd: OpenSRS API Question inbox
- Re: OpenSRS API Question inbox
- Re: OpenSRS API Question Csongor Fagyal
- Re: OpenSRS API Question Colin Viebrock
- RE: OpenSRS API Question Chris R Chapman
- Re: OpenSRS API Question Colin Viebrock
- Re: OpenSRS API Question inbox
- Re: OpenSRS API Question inbox
- Re: OpenSRS API Question inbox
- RE: OpenSRS API Question inbox
- Re: OpenSRS API Question inbox
- RE: OpenSRS API Question inbox
