FWIW, Items #1 and #2 are great ideas, and something that
*should* be implemented by OSRS as part of the generic
client. These make the generic offering easier for resellers
to customize in a way that is not so labor intensive.
I've often thought that the (frequent) upgrade process was
terribly unweildy because
(a) Resellers will, by design, make many modifications to
the basic client code, and
(b) Every new release includes many modifications sprinkled
throughout the code, requiring significant effort to
merge the two codebases. This applies to the .cgis as
well as the HTML templates.
This is why I'm still running the 2.2 codebase even though
I have 2.41 up and running in a test bay. I can't find the
time to merge all of my customizations back into 2.41.
#3 and #4, in my opinion, would address tasks that would
differ wildly from RSP to RSP and should be built by the
individual resellers.
Regards,
Eric Longman
Atl-Connect Internet Services
+-------------------------------------------------------+
| Atl-Connect Internet Services http://www.atlcon.net |
| 3600 Dallas Hwy Ste 230-288 770 590-0888 |
| Marietta, GA 30064-1685 [EMAIL PROTECTED] |
+-------------------------------------------------------+
----- Original Message -----
From: "Scott Allan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 07, 2001 9:07 AM
Subject: Re[2]: Wish List
William -
As usual you articulate your points well (and eerily close to our own
thinking), and I agree with most of what you say. I guess for the record I
would add that we do want to maintain a balance of improving the core API
and business logic, along with improving the client code (and RWI)
implementations. We do lean towards the API and core logic, but it is an
interesting challenge to balance these interests.
Regards,
sA
At 01:35 AM 9/7/01 -0700, William X Walsh wrote:
>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 ....."
>
<snip>
