Hi guys, thanks for starting this subject, I heard many valuable comments in this thread :)
>From the discussion, it's obvious that there is no single answer to needs of all people on the list, let alone quiet minority that's just observing. It's also obvious that we could do a lot more to help make our system more accessible. Instead of addressing every single point, let me give you few updates on what's happening platform-wise. Client code: We've lunched preview of the new generation of the client code towards the end of the last year. We continued with development, but since amount of feedback was very limited, we did not bother with another preview. However, and this is a good news, we are in the final stretch of development, and new PHP client version is coming "real soon now" (to borrow Chuck's trademark expression :). This will be official, supported version of the client code. However first release will not be including all the products that Tucows offers. Plan is to build up support for all the products and encourage migration of RCL users to this new code base. Until we have significant customer base migrated to the new version, both generations of the client code will be supported. There are some really neat stuff in the new client code version and I'm really excited. I hope you'll like it too:) API toolkits: One thing that I seem to be getting out of this discussion is that, if you had a good API toolkit that encapsulates complexities of communication (in the prog. language of your preference), you'd care less about API design. This is important, as it allows us to easier satisfy different needs of different resellers. New version of the client code comes with the nice PHP toolkit, and adding different language toolkits is an option that we're considering. However, this will be driven through ongoing evaluation process. There is always a tradeoff with resource deployment, so no hard promises here. New API: As some of you may be aware, we're using another API protocol for non-domain products (TPP for non-domains, XCP for domains). Since they are sufficiently different from each other, it's not really easy to get them together and create similar user experience. There is some integration work going under the hub, but all of this is long-term project. My preference would be to offer brand new generation of APIs, and run them in parallel to allow resellers to migrate on their own timetable. Again, this is long-term consideration, and not a firm proposal. In the meantime, you will see constant improvements to the existing API, but mostly evolutionary. Flame away now :), ------------------------------------ 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] Behalf Of > [EMAIL PROTECTED] > Sent: Wednesday, April 20, 2005 1:56 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Cc: [email protected] > Subject: Re: [domains-dev] OpenSRS XML documentation > > > I just realized there was a point in my previous comment > that needs to be more clearly stated: > > I personally feel that "implementation simpleness" should > be traded off with "definition simpleness". In other word > since multiple languages are trying to be targeted, as > well as those we can't yet know about because they do not > yet exist, I feel the "simple" answer is to right an > interface that might well be more difficult to code than > the current API *BUT* can be much more easily documented > and much more easily understood as to what it take to > perform a desired operation. > > So *I* don't mind more coding since I'll no longer be > thrashing around trying to understand why my "simple code" > [sic] does not work. ;) > > > > On Wed, 20 Apr 2005 00:24:00 -0400 > "Ross Wm. Rader" <[EMAIL PROTECTED]> wrote: > >On 4/19/2005 11:17 PM [EMAIL PROTECTED] noted that: > > > >>I can't help but feel that a really simple to interface > >>to API would be > >>a benefit to Tucows. > > > >I'd agree with that. It would be very helpful if "simple" > >was defined to some degree. > > > >-- > >Regards, > > > > > > -rwr > > > > > > > > > > > > > >"In the modern world the intelligence of public opinion > >is the one indispensable condition for social progress." > > - Charles W. Eliot (1834 - 1926) > > _______________________________________________ > domains-dev mailing list > [email protected] > http://discuss.tucows.com/mailman/listinfo/domains-dev > _______________________________________________ domains-dev mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-dev
