home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!olivea!hal.com!decwrl!pa.dec.com!decuac!hussar.dco.dec.com!mjr
- From: mjr@hussar.dco.dec.com (Marcus J. Ranum)
- Newsgroups: comp.protocols.tcp-ip
- Subject: Re: Implementation of Distributed Database in SUN RPC
- Message-ID: <1992Aug31.010015.1275@decuac.dec.com>
- Date: 31 Aug 92 01:00:15 GMT
- References: <1992Aug25.021602.22737@usl.edu>
- Sender: news@decuac.dec.com (USENET News System)
- Organization: Digital Equipment Corporation, Washington ULTRIX Resource Center
- Lines: 23
- Nntp-Posting-Host: hussar.dco.dec.com
-
- axk7110@usl.edu (Khanna Alok) writes:
- >I am working on implementation of a small model of distributed database.
- >I am planning to use SUN RPC for communication between
- >different clients and servers.
-
- Unless it's just going to be a toy, good luck. There are two main
- problems with Sun RPC for doing this:
- a) Unless you're using a multi-threaded RPC server, the
- server will fairly quickly become the bottleneck. Since it
- takes its requests in order of arrival, it's possible that the
- server will sit doing a big (for example) join that will
- take a while, while a request that would be very short
- has to wait.
- b) Since RPC does retransmit if it doesn't get an answer "fast
- enough" in case 'a' above, you may get multiple retransmits. The
- server then blindly redoes operations, unless you wind up writing
- a reliable delivery system, or using TCP RPC or something else.
-
- Generally, there are enough problems with using RPC (all fixable)
- that for anything other than a toy, by the time you've fixed them all,
- you might as well have not used RPC.
-
- mjr.
-