We (OSRS) would be able to re-enable access through the public manage
interface if necessary (ie, a reseller stops providing an interface).

This would be quite rare, and only manifest itself if a reseller were to
*disapear* and no longer be reachable.

Regards,


sA
Scott Allan
Director, OpenSRS
[EMAIL PROTECTED]

On Mon, 25 Mar 2002 [EMAIL PROTECTED] wrote:

> So what happens when the reseller goes away, or their scripts are
> offline for some reason, and the user cannot use the public manage
> interface at OpenSRS?
>
> -t
> --
> myOstrich Internet
> http://www.myostrich.net
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]] On Behalf Of Scott Allan
> > Sent: Monday, March 25, 2002 8:05 PM
> > To: POWERHOUSE
> > Cc: Mike Allen; Doug Friend; [EMAIL PROTECTED]
> > Subject: Re: DomainRegistryofAmerica???
> >
> >
> > On Mon, 25 Mar 2002, POWERHOUSE wrote:
> >
> > > True enough, but a *LOT* of people know that ANY RSP's Manage.cgi
> > > scripts will allow them to use their interface, so, I think
> > they need
> > > to make that NOT work, so that they have to use either The
> > RSP's that
> > > they registered the domain with, OR the public one at OpenSRS, for
> > > those Resellers who do NOT maintain a private one.
> > >
> > > I would like it though, that if the RSP DOES have a private one, as
> > > most of us do, then when they login to the public one, it uses
> > > LWP::Simple or something, and redirects them to mine, based
> > on what I
> > > set it to in the RWI. If NONE then do not redirect.
> > > Seems like it would be fairly simple.
> >
> > We are looking at enhancements like this, we will very likely
> > get to something in the next few releases..
> >
> > > Anyone know when Charles will get back from vacation? I can't
> > > remember, and I already deleted his email from my inbox and deleted
> > > folder.
> >
> > In an attempt to ensure he fully enjoys his vacation, this
> > information will remain classified. Your are stuck with me
> > until next week at least.
> > :)
> >
> > sA
> >
> >
>

Reply via email to