🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.client-server
Article #94

Designing a client-server systemm

#94
From: Robert Baynes
Date: Thu, 08 Oct 1992 12:17
54 lines
2776 bytes
I am in the midst of coding a client-server application using SUN's RPC.
Basically the system is a logger that receives requests from a client and
then sends them off to be logged. The requests consist of a procedure
(e.g. logIAabort) and several parameters. Once the logger receives the
request it  becomes a client to another  server that actually executes the
command and writes out to the log. 

The part described above is part of a much bigger system (a multidatabase
application). We want to distribute alll the major portions of the 
system such that no one part is required to reside with any other major
part on a particular computing node (hence the use of client-server).

Currently, for each client-server FAMILY (one server, many clients)
we have separate include files and separate client and server code 
(generated by rpcgen).



         IM ------>client----->IRS-------->client------->ILD
	    <------server-----<IRS<--------server-------<ILD

	1. The IM is compiled with client code to call IRS.
	2. The IRS is compiled with server code to respond its clients
	(IM in this case).
	3. The IRS is compiled with client code to call the ILD.
	4. The ILD is compiled with server code to respond to its
	clients (IRS in this case).

	The client code for 1 and 3 is different, as is the server
	code for 2 and 4. 


I give all of this to formulate my question: 

	Is there a clean way that we can generate the needed client 
	and server code (using rpcgen) such that all of the various 
	client software is in one source file and one include file 
	and all of the various server software is in another? 

Remember that some of our clients can act as servers so when we compile our application
code we would be including both the client and server code. 

I see possible compile time problems if we put together
the code together for 1 and 3 and 2 and 4. If we got around the compile
time problems the IRS, for example,  would then be compiled with all code 
(could it call it self??).

-- 
*******************************************************************************
	Bob Baynes		Department Of Computer Science
	rbb@cs.brown.edu	Box 1910, 115 Waterman Street
	(401)863-7684		Brown University
				Providence, RI 02912
*******************************************************************************
Technical Details
Message-ID: <1992Oct8.121748.4279@cs.brown.edu>
Path: arc1-ca.pugleaf.net!sparky!uunet!brunix!cs.brown.edu!rbb

Show Full Headers
Complete Article Headers
Newsgroups: comp.client-server
Path: arc1-ca.pugleaf.net!sparky!uunet!brunix!cs.brown.edu!rbb
From: rbb@cs.brown.edu (Robert Baynes)
Subject: Designing a client-server systemm
Message-ID: <1992Oct8.121748.4279@cs.brown.edu>
Followup-To: comp.client-server
Keywords: client, server, distributed systems
Sender: news@cs.brown.edu
Organization: Brown Computer Science Dept.
Date: Thu, 8 Oct 1992 12:17:48 GMT
Lines: 54