Thanks for the link!
My "beef" is with Tucows in that such descrenancies are not documented. Again, effectively, Tucows only supports a single configuration in a specific environment.
Why does enom provide such a "lite" and simple API? Answer: API is OS and Language Agnostic / enom is trying to avoid the limitations of complex API's like Tucows ......
Bottom line is that, according the the most recent State Of The Domain report (http://www.SOTD.info) enom gained 230,000 registrations (+0.6 market share) in Q4 2002 and GoDaddy gained 290,000 (+0.8 market share), while Tucows only gained 87,000 (-0.01 market share - a *LOSS*) ..... Sooner or later Tucows *WILL* provide an API that directly supports Windows Developement environment (I just wish it was sooner). Sooner or later Tucows will start catering to people like myself who personally own and administrate large blocks of domain names.
Thinking of a lightweight API, I am in favour of SOAP over HTTPS. Or something standard, let's not reinvent the wheel! SOAP runs on Java, Perl, PHP, C (raise your hand if it doesn't run on your platform :-)), etc.. Tucows uses XML anyway, the XML DTD-s are already there... Names4ever uses something like this (not SOAP, but something like a simple XML API). And why use a somewhat custom encryption with all the trouble if you have SSL? Ok, SSL is a bit slow on handhelds, but that is a marginal segment of the domain registration market anyway :-))
- Cs.
