Hi there, I've tried asking some difficult questions to [EMAIL PROTECTED] and not always got good (or sometimes any) answers. Thought I would share here and see if any other OpenSRS users had any ideas:
0) .at integration seems to be broken (OK only asked this yesterday but wasn't holding out hope) - I get 404 Command Not supported when trying to use the ADVANCED_UPDATE_NAMESERVERS command. Is this known about? 1) I don't understand the design decision behind the API potentially demanding a separate username & password for each domain you register with OpenSRS. We've always used a single username for all our domains, and it would seem that unless we kept a record of every single username and password, we'd not be able to manage them all automatically. Is there something I've been missing? The API document is very thorough on all the calls, but not so much on architecture, so wondered if anyone who's been working with OpenSRS for longer might be able to help. What's the advantage of assigning separate usernames for each domain, and how does it help the reseller? 2) I did a Ruby API : http://src.bytemark.co.uk/trac/ops-ruby We're using this on our live control panel and it works around lots of crumminess in the OpenSRS API design (sorry some NSFW source code as a result <g>). Here's some example code: rpc = OpenSRS::RPCQuick.live(username, password, key, true, OpenSRS::BasicDomainCache.new("/tmp/domain-cache", 864000) ) BYTEMARK_DEFAULT_CONTACT = { :first_name => "Bytemark", :last_name => "Hostmaster", ... etc. ... } # register a domain, throws exception if it doesn't work rpc.register_domain( "mysupernewdomain.com", BYTEMARK_CONTACT_SET, 2, # years true, # lock domain? ["a.ns.bytemark.co.uk", "b.ns.bytemark.co.uk", "c.ns.bytemark.co.uk"] ) renew another domain for 10 years rpc.renew_domain("myolddomain.com", 10) # OpenSRS UK integration is terrible, send it to a normal registrar rpc.set_uk_domain_tag("mydomain.co.uk", "BYTEMARK") This is an extra layer on top of OpenSRS::RPC which corresponds closely with the published API, which you can still use if you like pain <g> Anyhow if you want a Ruby API this is it, as far as I can tell. If anyone wants to flesh it out in the same cleaned-up style to support some of Tucows other features, I'd be more than happy to incorporate the changes, but I've only really implemented "core" features at the moment and not much other than .uk-specific Would be interested in any comments / answers on the above, especially from OpenSRS developers. -- Matthew _______________________________________________ domains-dev mailing list domains-dev@discuss.tucows.com http://discuss.tucows.com/mailman/listinfo/domains-dev
