Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!brunix!irwin!jhc
From: jhc@irwin.uucp (James H. Coombs)
Newsgroups: comp.databases
Subject: Re: Opinions on C-Tree (from the C-Tree mailing list).
Message-ID: <64036@brunix.UUCP>
Date: 7 Feb 91 14:39:08 GMT
References: <29809@usc> <63497@brunix.UUCP> <27ADAE15.3E99@tct.uucp> <472@oha.UUCP>
Sender: news@brunix.UUCP
Reply-To: jhc@irwin.UUCP (James H. Coombs)
Organization: IRIS - Brown University
Lines: 22

In article <472@oha.UUCP> tony@oha.UUCP (Tony Olekshy) writes:
>with application clients using IPC.  I have used the server with various Unix
>and with VMS (my DOS code runs single-user to date, although you get various
>LAN code in the distribution).  Note that this is not, apparently, the same
>server stuff being discussed by other posters to this thread, or else the
>posting about binary only servers is wrong--more later.

I think the server that you are talking about is the c-tree server.
With this server, the client side of the c-tree library sends all
low-level requests to the server side.  The speed improvement comes
from the buffering in the server and, perhaps, from locking records in
the process instead of through the OS.

The new "Faircom Server" accepts high-level requests from clients.  It
is multi-threaded.  There is a SQL version, which is really an API that
translates SQL into native-language requests.  I have not seen it, so
this brief description is based on my reading only.  Faircom verified
that licensing is for binaries only, although people should check for
themselves.  Oh, yes, this server supports transactioning and, I think,
some sort of access control.  I'm sure there are many more features.

--Jim