> We submit a request then
> wait.... did they receive it? was it accepted? we must wait for a
> reply... then when a reply is received, it must be parsed.
>
I don't know Nominet's system. Looks like they use a slow response system?
Before OpenSRS we have been dealing *only* with email-template systems and
I still prefer them very much over other systems. It's the main reason why
we don't use OpenSRS as our main provider for *new* com/net/org domains.
They provide for easier coding (building your own forms and submission
system), they provide for easy bulk processing, they provide for very good
documentation of activity because you get an email about every event.
Until now I haven't seen an OpenSRS reseller site which showed a
registration layout which was *truly* independent from the current client
offering. That shows me that many of the resellers *are* having problems
to code their own stuff and I'm sure this situation would be much relieved
with an email template system.
> Automating
> > the parsing on the registrar end is a much greater task then getting a
> > result back from a real-time API.
>
I assume you mean RSP's end? Actually, it's very easy. Of course, those
replies would contain certain error codes which would clearly identify
success, failure etc. You just need to pipe such an email to an amazingly
small perl script to have your own mail robot running.
Kai
--
Kai Sch�tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org
ClubWin - Help for Windows Users: http://www.clubwin.com
