NAME

WWW::eNom::Role::Command - Basic Logic for Submission of Requests to eNom

SYNOPSIS

    use WWW::eNom;

    my $eNom     = WWW::eNom->new( ... );
    my $response = $eNom->submit({
        method => 'Check',
        params => {
            DomainList => 'drzigman.com, drzigman.net, enom.biz',
        }
    });

WITH

WWW::eNom::Role::Command::Raw

WWW::eNom::Role::Command::Contact

WWW::eNom::Role::Command::Domain

WWW::eNom::Role::Command::Domain::Availability

WWW::eNom::Role::Command::Domain::Registration

WWW::eNom::Role::Command::Domain::Transfer

WWW::eNom::Role::Command::Domain::PrivateNameServer

WWW::eNom::Role::Command::Service

REQUIRES

response_type

DESCRIPTION

Primary interface to eNom API that is used by the rest of the WWW::eNom::Role::Command::* roles. The only reason a consumer would use the submit method directly would be if there was no corresponding Command for the needed operation.

METHODS

submit

    use WWW::eNom;

    my $eNom     = WWW::eNom->new( ... );
    my $response = $eNom->submit({
        method => 'Check',
        params => {
            DomainList => 'drzigman.com, drzigman.net, enom.biz',
        }
    });

The submit method is what sends requests over to eNom. It accepts a raw method and an HashRef of params. For details on the structure of the params please see WWW::eNom::Role::Command::Raw.

The submit method returns a HashRef that represents the data returned by eNom. There is logic built into submit such that requests are always made with an xml_simple response_type which is what drives the creation of the HashRef to form the response.