Der bei weitem “lustigste” Prozess ist der der switch.ch, der Schweizer Registry. Dort sind nicht nur finanzielle und organisatorische Hürden zu nehmen (und auch die sind nicht zu knapp) sondern auch ein technischer Parcours.

Dieser Parcours (der heißt wirklich so) besteht aus 23 epp transactionen (Querbeet, dh personen, hostobjekte, domains anlegen, löschen und so weiter) die einem Durchgang durchzuführen sind.

Das bedeutet, daß jeder Registrar neben des Implementierungsaufwands für den normalen Clienten, sich nochmals zwei Tage (solange habe ich alles in allem gebraucht) Zeit & Geld nehmen darf um den Parcours zu implementieren. Man muß allerdings auch wirklich zugeben, wenn man den Parcour implementiert (und somit verstanden) hat, daß man auch die Prozesse der switch “durchschaut” hat.

The giturl you’ll find the code at is

http://github.com/MarkHofstetter/php-epp-client

remarks/comments/suggestion are very welcome

hopefully I did not forget any features/request types. The most interessting new feature is the web client, which is in my oppion easy to use and really usefull for small scale registrars

so the new feature for this release are

• web client
• all request types (hopefully)

what is still lacking is reasonable error handling, support of severel registrars and possibly multi client capabiltiy, when installing please be carefull that your php.ini(s) include openssl/ssl support

for more information please go to  the php-epp-client main page

new feature(s);

• a command line client

shell> php client.php epp-config.xml domain-info
domain : bla.at
trid : 123

<?xml version="1.0" encoding="UTF-8" standalone="no" ?><epp xmlns="urn:i
e" xsi:schemaLocation="urn:ietf:params:xml:ns:epp-1.0 epp-1.0.xsd">
<response>
<result code="1000">
<msg>Command completed successfully</msg>
</result><msgQ count="1" id="296463033"/>
<resData>
<domain:infData xmlns:domain="urn:ietf:params:xml:ns:domain-1.0" x
<domain:name>bla.at</domain:name>
<domain:roid>bla.at</domain:roid>
<domain:status s="ok"/>
<domain:registrant>FS1533880</domain:registrant>
<domain:contact type="admin">FS1533880</domain:contact>
<domain:contact type="tech">NIS1494123</domain:contact>
<domain:ns>
<domain:hostAttr>
<domain:hostName>ns1.nessus.at</domain:hostName>
</domain:hostAttr>
<domain:hostAttr>
<domain:hostName>ns2.nessus.at</domain:hostName>
</domain:hostAttr>
<domain:hostAttr>
<domain:hostName>ns3.nessus.at</domain:hostName>
</domain:hostAttr>
</domain:ns>
<domain:clID>Reg326</domain:clID>
<domain:upDate>2006-05-23T08:52:53.00Z</domain:upDate>
</domain:infData>
</resData>
<trID>
<clTRID>123</clTRID>
<svTRID>2009012811122133516239-992-nicat</svTRID>
</trID>
</response>

</epp>

1000
Command completed successfully

shell>

This is so 90s!

So I thought of doing it with a little php and Ajax using the finger tool (or something similar) provided by most registries. Taking this opportunity I also tried it in three different ways to check which Ajax Framework to use.

See how it works

The oldfashioned way - by hand

See the code here, a little clumsy

The Sajax Framework

See the code here, the Framework is quite new, and honestly I didn’t get the code to work on this server, it worked nicely with a XAMPP installation on windows, but neither on OpenSuse 10 nor on AIX 5.3. The callbacks are also an nuisance i.e. that you have to code them yourself.

The xajax Framework

See the code here. This is the shortest and most elegant code by far. Coming from the examples it took me about three minutes to adapt the example. For me the clear winner of this short comparison