I try to do my very best to avoid ad-hominum arguments, but frankly.... Your statement "it matters to everyone who is integrating a domain business into their operations..." is just exactly that.
You aren't addressing what you perceive as an impossible flaw in the technology. You're saying that you need this because you are trying to do business, and I don't need it because it logically follows that I'm not. To extend your argument, no one can use any port for any purpose -- we have to stick to a few well-known ports. OpenSRS is doomed to failure because they don't do TLS on port 80, or SSL on pport 443. I don't see how this differs from what used to be the main argument: Writing a client in Perl means that no one but a Unix admin. can run the client. .. and while a number of folks were complaining about how difficult that was, Eric Longman (along with a number of contributors) ignored them and produced a document that explains exactly how to make the client work, and included the necessary modules so they could be easily installed in PPM. Sadly, this isn't really a developers-list anymore, it's more of a place where people can complain about how Tucows did everything wrong and therefore in danger of becoming irrelevant. We have integrated domain registration into our business. It's working nicely, thank you very much. -- Lynn On Mon, 27 Oct 2003 15:31:48 -0500, [EMAIL PROTECTED] wrote: >>>The people who are complaining are complaining because OpenSRS doesn't >�do "x" where "x" is their favorite thing. > >�I'm advocating for XML WEB Services because the OPENSRS system does not >�use ANY standards - it connects to a non standard port, communicates >�using a homegrown protocol that has encryption embedded into it. I think >�all developers on all platforms would benefit from the utilization of >�W3C protocols - HTTP, XML, SOAP, SSL, etc. This makes it easier for >�everybody to build clients that integrate into their environments and >�business practices. If you have to become a Crypto and TCPIP sockets >�guru to develop a non-Perl/PHP client, not many clients are going to be >�developed. > >>>>>because frankly, it doesn't matter. >�This matters to everyone who is integrating a domain business into their >�operations. It should matter most to Tucows, as they want their service >�to be available to the widest possible client base. > >>>The important point is this one: "The nice thing about standards is >�that there are so many to choose from." > >�We agree completely - which one(s) are you advocating? > > >�John Roche >�einfosystems.net > > >�This mail was content checked for malicious code and viruses by >�GFI MailSecurity. GFI MailSecurity provides email content checking, >�exploit detection and anti-virus for Exchange &�SMTP servers. Email >[EMAIL PROTECTED] for more information.
