Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!decwrl!sun-barr!newstop!east!hinode!geoff From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) Newsgroups: comp.protocols.tcp-ip Subject: Re: Are sockets the wave of the future? Message-ID: <2487@east.East.Sun.COM> Date: 27 Aug 90 00:54:29 GMT References: <1990Aug25.183437.1@rogue.llnl.gov> <1990Aug26.065346.13988@Solbourne.COM> <8076:Aug2616:42:1890@kramden.acf.nyu.edu> Sender: news@east.East.Sun.COM Reply-To: geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top) Organization: Sun Microsystems PC-NFS Engineering Lines: 22 Quoth brnstnd@kramden.acf.nyu.edu (Dan Bernstein) (in <8076:Aug2616:42:1890@kramden.acf.nyu.edu>): #auth provides that advantage without that disadvantage! Again, it was #designed for client-server applications, unlike RPC. [smiley mode on] Dear Dan, You seem to understand these things, so maybe you can help me with a little semantic problem. Every time I feed a .x file to rpcgen, it insists on spitting out client and server stubs, which I find convenient for building my distributed applications. Yet you say that RPC wasn't designed for client-server applications. I'm confused... Geoff Arnold PC-NFS architect -- Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff@East.Sun.COM) -- To receive a full copy of my .signature, please dial 1-900-GUE-ZORK. Each call will cost you one zorkmid.