I realize that Tucows has to maintain backward compatibility,
That can be the problem itself. :( Sometimes the pain of a compelete rewrite is the best way to go. Given Tucows creation of the vary notion of pass through "reseller services" it makes sense that Tucows was written in the langauge it was back then and has in fact stood the test of time. But times have changed and you have oddballs like me using very non-standard environments such as Clarion (see: www.SoftVelocity.com).
I think a complete rewrite much well be in order and thus I think there is little choice but to have multiple APIs. That is, as you say, the old / original must move forward given how entrenched it is. And then a nice simple "enom type" interface for people like me that just want to wip up simple brain dead apps that can't do everthing but can do all the basic stuff we all do day in and day out to manage domains -- The stuff that you find in common with *ALL* registrars admin interfaces; whois change, DNS change, lock and unlock, register a domain (just use account defaults and I'll use the other functions to fix the fields the way I want). You don't even have to give me block operations after all that's why GOD invented the LOOP/END structure. ;) So I'll just run a loop to do my block operations.
_______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev
