There's nothing wrong with placing your own systems between your customers
and OpenSRS - it ensures you keep your customers, and they don't jump ship
before paying for the services you're getting. I know of several RSPs
doing this already :)
Charles Daminato
TUCOWS Product Manager (ccTLDs)
[EMAIL PROTECTED]
On Thu, 15 Feb 2001, Dave Warren wrote:
> > >Password retrieving feature:
> >
> > >b) Incase the user changes his password / email address after registering
> > >the domain, the same is updated to the database in your server.
> >
> > How this is possible, if the user change his/her password / email
> > at http://manage.opensrs.net/
>
> It likely isn't. However, keep in mind that if you don't tell users about
> that, and you've redone the look of the site, many/most people won't know
> about OpenSRS's relationship. Only the most tech-savvy will, and frankly,
> those people are much less likely to lose passwords then run of the mill
> (l)users.
>
> Another option, to enforce using their interface, you could prepend the
> password with a single string inside your interface. This will require
> users to use your interface (only) to make changes. I don't know whether
> this violates any OpenSRS rules/regs though.
>
> Just from personal experience that is.
>
>
> ========================================================
> Dave Warren
> Email: [EMAIL PROTECTED]
> Free POP3 and WebMail at: http://webmail.devilsplayground.net/
> ========================================================
>
>
>
