Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DEFAULT_SERVICES #1

Closed
avatar opened this issue Apr 25, 2013 · 4 comments
Closed

DEFAULT_SERVICES #1

avatar opened this issue Apr 25, 2013 · 4 comments

Comments

@avatar
Copy link

avatar commented Apr 25, 2013

Hi,
I tried to add services like mentioned in the source of client.rb

services = EPP::Client::DEFAULT_SERVICES + %w(urn:ietf:params:xml:ns:secDNS-1.1)
EPP::Client.new('username','password','epp.example.com', :services => services)

but it does not seem to work. I get

uninitialized constant EPP::Client::DEFAULT_SERVICES

I also tried to do this:

services = %w(
     http://www.dns.be/xml/epp/dnsbe-1.0
     urn:ietf:params:xml:ns:domain-1.0
     urn:ietf:params:xml:ns:contact-1.0
     urn:ietf:params:xml:ns:host-1.0)
EPP::Client.new('username','password','epp.example.com', :services => services)

But no luck...

Can you please point me in the right direction?

Thanks a lot!

Ben

@geoffgarside
Copy link
Contributor

Are you using the version from git or from rubygems? Version 0.0.3 predates the reorganisation. I'll be releasing the git version as 0.1.0 in a couple of weeks.

@avatar
Copy link
Author

avatar commented Apr 25, 2013

I am using version 0.0.3 from rubygems.

edit: sorry, i accidently closed the issue... :/

@avatar avatar closed this as completed Apr 25, 2013
@avatar avatar reopened this Apr 25, 2013
@geoffgarside
Copy link
Contributor

You can use EPP::Server::DEFAULT_SERVICES in v0.0.3, but I'm trying to keep Server as an internal object now. This constant will still work in the next version, but it will emit a warning.

The :services option should be passing the services list down to the Server instance, these are then sent in the login command. The debug-ability of v0.0.3 is pretty poor in comparison to the latest version. If you can try the git version that might suit better, I've not found any issues with it yet with the exception of an occasional Errno::EINVAL error during the TCP connect process, but I think this is more related to the server I'm connecting to.

@geoffgarside
Copy link
Contributor

Closed since 1.0.0 was released in June 2014.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants