There is also the kickass PHP version of the OpenSRS client ( credits to Colin Viebrock for developing/maintaining this )
http://sourceforge.net/projects/opensrs-php/ > Mark, > > There's no need to build your own client, we have one already :) Of > course, you *can* write your own, this all depends on how you want to > implement. I suggest you go through this: > > http://resellers.tucows.com/opensrs/documentation > > Paying particular attention to the Perl Client Manual (and the New User > Guide, of course!) > > And then check out here: > > http://resellers.tucows.com/opensrs/resources/download/current/ > > And then, when you're ready: > > http://resellers.tucows.com/opensrs/resourcedirectory > > :) > > Charles Daminato > TUCOWS Product Manager > [EMAIL PROTECTED] > > On Thu, 18 Jul 2002, Mark Fowkes wrote: > > > Hello All > > > > You'll have to excuse me if this is a question that's been asked many a time > > before, or im missing something on the opensrs website, this is my first > > post to the list, and I joined only 24 hours ago. > > > > I work at an ISP in the UK, we have registered around 3000 domain names for > > our customers. We have recently moved over to OPENSRS. We have our systems > > here to register domains, for .co.uk's we use Nominet - we compile an email > > here on the fly, encrypt it - and send it to nominet who then reply once its > > registered or if there is an error. > > > > Im pretty sure OPENSRS don't run a similar system, and the only thing I can > > find is their Perl modules that you place on your "website" they then > > connect to OPENsrs. That's not really any use for use, as we already have > > our order system in place for domains, we just need an automated way of > > registering them? > > > > Ive seen in there documentation there is a section for "Writing your own > > client" and it tells you to read there protocol specification document > > (which is where?) > > > > Regards > > > > Mark Fowkes > > > -- /Em Progress is not intelligently planned
