I'm in favor of Tucows using their energy to produce a webservice accessible via SOAP or HTTPS. In fact I am working on such a project now in VB.Net. That would be a platform and language neutral solution, which also adheres to open standards. We(as in the dev community here) could supply a variety of client software, opening up a whole new profit center in the process. There are always the open source Perl and PHP clients for those who want free software. The Tucows folks could concentrate on adding features to the webservice like WS-Security, etc.
I was able to write a web client in a few hours for the amazon.com web service to search for books and CDs. Windows is definitely the ugly stepchild here, we will fix that in a few months. Of course, it would be nice to know what Tucows' plans are, so we are not duplicating efforts. John W Roche eInfosystems.net >> Again, effectively, Tucows only supports a single > configuration in a specific environment. >> 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...
