Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!linus!alliant!mrmarx!gra
From: gra@mrmarx.UUCP (Gary Adams)
Newsgroups: comp.lang.c++
Subject: External Data Representation (XDR) Class Wanted
Message-ID: <604@mrmarx.UUCP>
Date: Tue, 22-Sep-87 19:05:05 EDT
Article-I.D.: mrmarx.604
Posted: Tue Sep 22 19:05:05 1987
Date-Received: Fri, 25-Sep-87 07:18:31 EDT
Reply-To: gra@mrmarx.UUCP (Gary R. Adams)
Organization: Decision Software Co, Cambridge, MA
Lines: 19
Keywords: XDR NFS c++ stream X

I just started to build my first class derived from the basic 
streambuf ("stream.h") that would provide the XDR (NFS data exchange)
protocol functions in a stream oriented fashion. It looks fairly straight
forward to do, so I thought I would check with the net to see if it has 
already been done before . Any hidden gotchas to avoid ?

There are a few things that appear to be "text" file restrictive in the
istream and ostream classes that make it necessary to build on the streambuf
definition directly. Ultimately I would like to be able to construct a variety
of "record streams" that are both machine and transport independent that
could be used for server-client communication (e.g. X like) over ethernet, 
decnet, message queues, LU 6.2, etc.

Thanks in Advance.
-- 
Gary R. Adams			{masscomp,alliant}!mrmarx!gra
Decision Software Company	
51 Spinelli Place		- ski the trees ! - 8:-<>>  -
Cambridge, MA 02138		"They'll be no tribble at all."