Thursday, Thursday, September 06, 2001, 11:25:12 PM, [EMAIL PROTECTED] wrote:
> 1) Move all unique configuration to a user.conf file so that we don't
> have to re-edit so much on each upgrade
> 2) Remove appropriate formatting from the html so that we can use css etc
> to customise the look and feel consistently without editing all the
> templates directly
> 3) Add a shopping cart so that we can associate and sell other services
> such as SSL certs and hosting at the same time we sell the domain name. I am
> sure this will dramatically increase the sales of the certs, it will also
> mean that we only need to handle payment the processing parts. A money
> spinning opportunity for Tucows or Resellers to sell the payment processor
> add-ins and a high confidence that the shopping cart would always work with
> the registration engine. I would imagine that most resellers would happily
> pay for this component !
> 4) T's&C's link for appropriate tld in the confirmation page and change
> the wording to "I have read and accept the Ts&C's ....."
Would you like fries with that too? :)
OpenSRS provides the API and a sample client code, all of the
functionality you asked for can be implemented by RSPs on their own,
and they have the option of sharing those implementations here (like
many of us have).
I'd be more interested in server side enhancements, and OpenSRS
providing a basic set of API implementations, like they have, and
letting the RSPs distinguish themselves from each in other in how they
implement it.
Some RSPs are very creative about this, I've seen some very interested
implementations.
RSPs who want to stand out have to distinguish themselves from the
pack.
For what it is worth, there are "domain shopping cart" programs out
there that work with the OpenSRS system. Namebrain has an excellent
one, that works quite well, for instance. Another RSP on this list
did one with PHP, and then when they are ready to check out, it calls
the reg_system.cgi script as a bulk order with the domains in hidden
fields. A rather creative, and yet simple to implement, solution.
I'd rather see OpenSRS handle server side enhancements, such as better
ability for RSPs to download more complete domain data via CSV, the
various things we have seen mentioned regarding whois, and the per
transaction flags in the API, and other server side or API issues.
Remember, the OpenSRS client is just a sample implementation of the
OpenSRS API. What we do with it is what distinguishes us from just
those who can ftp up a CGI script to their website and enter a chmod
command.
Creativity is required, for sure, and some basic coding skills. Or at
a minimum, the ability to pay someone else who has those things.
--
Best regards,
William X Walsh <[EMAIL PROTECTED]>
Userfriendly.com Domains
--
