> 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.
