|
Hi Zeljko, The API functionality and range of features is great - no complaints on that front. As an application service provider, we are fully aware of and sensitive to compatibility issues and version management. The problem is the data structures being returned. Why couldn't Tucows maintain the current backoffice system but enable the API to return proper XML based on a submitted request value? We provide this type of functionality to our clients using our various APIs to ensure maximum compatibility with our clients/service consumers. Am not asking for a "Baskin Robbins 1000 flavors" capability, just an industry standard XML schema. Brad Thompson Zeljko Dimic wrote: Hi Brad, improvements to API are always possible. However, keep in mind that issue of backward compatibility is extremely important to us. We have thousands of customers that use using API and have developed it at different points of time. For that reason, we're developing new features in such a way that any improvement is backward compatible and only adds stuff, never subtracts; existing production systems of our partners are therefore safe. However, for that reason 'redoing' XML responses is not an option with current generation of the APIs.What may happen down the road is that we introduce cleaner and easier to use new API; this one would operate in parallel to existing one. Such approach would allow both old and new customers to safely develop against new API, while existing production systems continue humming unaffected. To this effect, we've had some internal discussions, but nothing firm yet. ------------------------------------ Zeljko Dimic Technical Product Manager [EMAIL PROTECTED] Tucows Inc. 96 Mowat Avenue Toronto, ON, M6K 3M1 Canada tel: 416.535.0123 x 1256 fax: 416.531.5584 ----------------------------------- -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Brad Thompson Sent: Friday, April 15, 2005 7:38 AM To: [email protected] Subject: Re: [domains-dev] OpenSRS XML documentation What you will find, if you are not using perl, is that the Request XML is good. However, the returned Response XML is horrific to work with. Effectively, it is a perl structure wrapped with XML tags that are not clear nor descriptive. Tucows - When is the api going to be cleaned up to provide usable XML packets? Brad Thompson [EMAIL PROTECTED] Dash One Christian Roy wrote: Hello Edward, the documentation is called "OpenSRS API Specification" and it's available in the documentation section of the Reseller Resource Center (RRC): https://rrc.tucows.com/documentation If the API that tucows provides (in perl) isn't in the language that you need, I recommend googling for the API in your language. I saw API in PHP and ASP and I wouldn't be surprised if there's an API in other languages. Good luck in your project. On Thu, 14 Apr 2005, Edward Muller wrote: Is there any documenation of the XML protocol used for OpenSRS? We are interested in writing a registration and management package of our own. We are already a Tucows reseller. Thanks! -- Edward Muller - Interlix [EMAIL PROTECTED] 417-862-0573 PGP Key: http://interlix.com/Members/edwardam/pgpkeys Christian Roy <[EMAIL PROTECTED]> Président Station InfiniWeb inc. http://www.infiniweb.ca /* Hébergement Web - Programmation Web - Sites Web - Nom de domaine */ /* Web Hosting - Web Programming - Instant Websites - Domain name */ -- Brad Thompson [EMAIL PROTECTED] www.dashone.com Office: 703.830.9647 _______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev --
| ||||
<<inline: email_logo.jpg>>
_______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev
