CLOSE BUT NO CIGAR.....
Yes the Web Server and browser are working as client server BUT
R:Base/Oterro ONLY RESEMBLES C/S IF and ONLY IF you maintain the R:base data
files on the same server as your Web Server. Since you really don't want to
keep your R:Base files on the same system as your Web Server (performace,
security, scalability) Oterro will have to drag data across the network. If
you plan on doing any sort of load balancing you will have to maintain the
datafiles on a different server. You might even get better response by
maintaining the RB files on a separate server since your Web Servers would
be configured as application servers while your R:Base server would be
configured as a file server. In any case R:Base/Oterro is not C/S.
What I can not figure out is why every one keeps trying to change R:Base
into something it is not. Use the right tool for the job. R:Base fits its
niche very well. If you need more horsepower, get the right tool.
PS.
I suppose it all depends on how Razzak defines the "BIG" environment. R:Base
is great in its market, but lets be realistic and not try capture the next
TPC-D record.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Bill Downall
Sent: Tuesday, May 29, 2001 1:09 PM
To: [EMAIL PROTECTED]
Subject: RE: R:BASE Web Front End
And notice that in the model Paul describes, Oterro being used on a
web server to serve R:Base data to browsers through Oterro or any
other front end, is, in fact, working as a Client/Server database.
Bill
On Tue, 29 May 2001 15:42:44 -0400, Ravina, Paul wrote:
>Think of it this way: in a desktop database, you can have your data
on a
>server, but there are no smarts up there. Suppose you wanted the
average
>amount of column X from a table. You would be downloading
everything from
>that table to your local workstation, and then calculating the average.
