Pre-release documentation is available - check the archive for this
list...
On Sat, 19 Aug 2000, FerLists wrote:
> > Easier said than done. I like the way Authorize.net (and I think this
> other
> > registrar) does things. You post and the results are returned in a coma
> > separated text that I can parse and do with what I like.
>
> Could you give us the name of the "other" registrar. I'm giving up hope that
> OpenSRS will release documentation of how we are supposed to send requests
> and what format the results are returned in so that we can make our own
> client software in whatever language we want.
>
> It would be almost as easy to open a port into the OpenSRS system as it
> would be to do an http post, but the problem is they still won't give us the
> commands or the format of the results they send back.
>
>
> > > Setup the default OpenSRS perl scripts on your server somewhere without
> > > integration into a credit card system, make sure they are in a password
> > > protected directory, then post to that location from your own ColdFusion
> > app.
> > > You don't have to mimic all of the steps for the registration, just
> mimic
> > what
> > > the "verify" page returns to the reg_system.cgi script.
> > >
> > > I went a step further and modified the template on reg_system to print
> out
> > some
> > > status info easily parseable by my script.
> > >
> > > It worked fine for me...
>
> Better yet, OpenSRS could spend 2 or 3 hours to write and release the
> protocol documentation so we don't have to go through such loops.
>
Thanks,
-rwr
Ross Wm. Rader
Director Product Management,
Channel Platform Group
Tucows Inc.
[EMAIL PROTECTED]
t. 416.535.0123 x335
f. 416.531.5584
"Embrace the cow, love the cow.
And remember, Winsock means love."
