Well, the RWI was initially built as a domain portfolio/customer management interface
The client code was initially built as a transaction entry method and domain/product management (create/modify/renew) interface As we grew we tried to keep these together, but more and more features from the client code crept into the RWI Hence the reason to revisit and create more RWI-ish features in the client code. Note that providing full data access via the API opens the door to potential abuse, so we have to be sure we do it right :) In the interim, people have found themselves attempting to automate activities only done via the RWI by using a script (hacked API) It's the transition that we'll have to be careful of :) Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Dave Warren > Sent: July 17, 2002 3:29 PM > To: Charles Daminato > Cc: Phillip Beazley; [EMAIL PROTECTED] > Subject: Re: Low Priority Request > > > Maybe I'm missing something important, but why does the RWI need to be > scriptable at all? Couldn't all functions be put into the API, > completely eliminating the need for the RWI? > > Don't get me wrong, you'd still need the RWI hanging around, but there > really shouldn't be any need to script it, ever, should there? > > Charles Daminato wrote: > > We could do "both" for a period of time, but maintaining two seperate > > interfaces (that perform the same functions) becomes more and more > > troublesome after time. > > > > But there would definitely be a transition period (details to be worked > > out). > > > > :) > > -- > The nice thing about standards, there is enough for everyone to > have their own. > >
