I wonder why we have to make this so complex. Actually I know why because
this is written by programmers :) Anyway I would like to direct attention to
the developers guide from Authorize.net. It is very clear and concise.
http://www.authorizenet.com/go2/framed.php3?url=secure.authorize.net/docs
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 th
> 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
Personally, I think that the nice API OpenSRS provides for us is
vastly superior to some cheesy HTTP-based hack. Please don't talk
them into such a thing. :-)
It's funny that you used the word "proprietary", which means "used,
made, or marketed by one having the exclusive legal right". The
Open
ROTECTED]>
To: "Neil H." <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, August 07, 2000 3:18 PM
Subject: RE: HTTP Post option
>
> "Neil H." wrote:
> > Point is we need an HTTP Post type system to register domain names. It
> > would
H." <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, August 07, 2000 3:00 PM
Subject: Re: HTTP Post option
> We cannot really do this without removing a layer of security from the web
> based interface - there's no simple way for us to do authentication with
&
"Neil H." wrote:
> Point is we need an HTTP Post type system to register domain names. It
> would be nice to have such an option. It would take me all but about 15
> minutes to create a system that would integrate with OpenSRS and Cold
> Fusion. In perl it would take me weeks.
Setup the defau
Point is we need an HTTP Post type system to register domain names. It
would be nice to have such an option. It would take me all but about 15
minutes to create a system that would integrate with OpenSRS and Cold
Fusion. In perl it would take me weeks.
Neil
p.s. I am not looking for bulk regi
PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, August 07, 2000 1:11 PM
Subject: Re: HTTP Post option
> Our API is somewhat documented, with a much better version coming up in
> the next month (with grossly improved documentation).
>
> You 'can' do HTTPS posts to the
We cannot really do this without removing a layer of security from the web
based interface - there's no simple way for us to do authentication with
this method.
"Neil H." wrote:
>
> Point is we need an HTTP Post type system to register domain names. It
> would be nice to have such an option. I
You can POST directly? an example would be nice... my "active domains"
robot has to login to get a cookie, and then proceed with "normal" web
operations... (I guess those operations might be combinable, much as the
API indicates for client operations)
Neil, I'm sure there are _lots_ of people on
Our API is somewhat documented, with a much better version coming up in
the next month (with grossly improved documentation).
You 'can' do HTTPS posts to the web based interface you get with an
account - but this has semi-limited functionality (i.e. unable to do batch
registrations/transfers).
"
I just found another Names provider that allows HTTP post options to
register domain names. Is Open SRS looking into such a thing? I mean it
seems very proprietary to only give code in PERL. I am not nor will I ever
be a Perl developer. If we could use ANY technology to post via HTTP
(preferab
13 matches
Mail list logo
