True... only problem being, batch.opensrs.net is functionally identical to
rr-n1-tor (on purpose) in case we need to "steal" the machine to put into
the regular pool.
So it'll be difficult to have it different. We may place an "old RWI"
interface at a different URL (http://resellers.opensrs.net/old for example)
as part of the transition.
It's all gotta be worked out :)
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - chuck@tucows.com
> -----Original Message-----
> From: owner-discuss-list@opensrs.org
> [mailto:owner-discuss-list@opensrs.org]On Behalf Of bill@daze.net
> Sent: July 17, 2002 1:00 PM
> To: discuss-list@opensrs.org
> Subject: RE: Low Priority Request
>
>
> > It's a big project though, and our timelines are currently
> unknown. Since
> > many resellers rely on the RWI to grab data [1] (many even automagically
> > with Curl or LWP/SSLeay) we have to ensure we either do a slow
> transition or
> > attempt to keep backwards compatability (which will make major updates
> > difficult, but we'll work it out)
> >
> > [1] all scripting against the RWI *must* go to
> batch.opensrs.net to avoid
> > breaching the AUP :)
>
> There is your solution... The RWI available via batch.opensrs.net could be
> the old scriptable interface and the non-batch, non-scriptable RWI (via
> rr-n1-tor.opensrs.net) can be the new and improved UI.
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:20 EDT