On Wed, 7 Mar 2001, Csongor Fagyal wrote:
> Tom: How about using the Perl API? Isn't that easier to use then emulating
> https calls?
The look I did over the API used by the client code was that it wouldn't
do much of anything at the reseller level. Its functionality pretty much
maps into what register.cgi and manage.cgi need... in short: yes I did
look ... but at 100+ pages I didn't look all that thoroughly. (And the
original poster may have looked too, since he refered to client
id/passwords and most of the API requires those to do anything [like
manage.cgi].)
> Charles: It seems to me that setting up one CGI script which gives back only
> the most important data in some delimited text format should not take more
> than a day, once someone is on the server-side and is familiar with the
> system...
I was going to comment on that and forgot. I can can't image that taking
the view_domains functionality, stripping the HTML from it, and removing
the 40 at a time limiting logic could take much more than about
30 minutes** ... multiply that by 3.14159 to get a number safe to use in
the consulting world, and we can safely assume that we've spent more time
talking about it than it would have taken to implement... certainly it
took me longer to write the sslbot than it would have taken OpenSRS to
implement (which is the main reason for my bad attitude about this still
being an issue).
** - assuming that openSRS is using a reasonable development environment
and not doing something silly like entering machine opcodes in hex...
given that the RWI identifies itself as mod_perl, that seems a safe bet.
Heck... Chuck, send me the subroutine that implements view_domains and
I'll edit it for you :-) ... (Yes, I'm "mod_perl safe").
----------------------------------------------------------------------
[EMAIL PROTECTED] | Don't go around saying the world owes you a living;
http://BareMetal.com/ | the world owes you nothing; it was here first.
web hosting since '95 | - Mark Twain
