home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.client-server
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!cbnewsm!cbnewsl!sdo
- From: sdo@cbnewsl.cb.att.com (scott.orshan)
- Subject: Re: SQL and Client-server architecture
- Organization: UNIX System Laboratories
- Date: Tue, 17 Nov 1992 16:07:48 GMT
- Message-ID: <1992Nov17.160748.5948@cbnewsl.cb.att.com>
- References: <92316.105420KSADEGH@auvm.american.edu>
- Lines: 31
-
- In article <92316.105420KSADEGH@auvm.american.edu> Kayvon Z. Sadeghi <KSADEGH@auvm.american.edu> writes:
- >Hi out there
- >
- >I was wondering why all the client/server systems use SQL as their manipulation
- >language. I don't recall seeing any client/server that works on OO or
- >hierarchy, for example. Is this because its easier to implement client/servers
- >in SQL or is there any especial reason.
- >
- >I would appreciate if someone could give me some pointers on this.
- >------------------------------------------------------------------------
- >Kayvon Sadeghi k.sadeghi@ieee.org
- >Voice:202/244-0789
-
- I'm not sure why you say that all client/server systems use SQL.
- Perhaps all client/server SQL database systems use SQL (a tautology),
- but some databases don't, and non-database client/server packages
- probably have no need to use SQL.
-
- For example, plain RPCs and TP Monitor C/S calls pass arbitrary information
- between clients and servers. Most client/server access is probably
- just remote file access, and that has nothing to do with SQL.
-
- Even C/S SQL databases don't always pass SQL. If a stored procedure is
- being invoked, then the message need only include the name of the
- procedure.
-
- Scott Orshan
- TUXEDO Support
- UNIX System Laboratories
- 908-522-5063
- sdo@usl.com
-