Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!ll-xn!ames!oliveb!amiga!cbmvax!jesup
From: jesup@cbmvax.UUCP
Newsgroups: comp.sys.amiga.tech
Subject: Re: Resources, sets, and abstract datatypes
Message-ID: <3826@cbmvax.UUCP>
Date: 19 May 88 17:48:06 GMT
References: <5920@well.UUCP> <957@sandino.quintus.UUCP> <5483@utah-cs.UUCP> <10881@steinmetz.ge.com>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 19
Posted: Thu May 19 13:48:06 1988

In article <10881@steinmetz.ge.com> guilford@turing.cs.rpi.edu (Jim Guilford) writes:
> I would suggest the
>following: you add one reguired function to the library vector. This
>would be a name mapper. When one first loaded the library (ADT), one
>would pass the mapper a string for each command you expected it to
>have. The mapper (who knows what is actually in the library) would
>pass back the address of the function which implements it (or NULL if
>it is not implemented).

	Jim:  You've just re-invented the Sun RPC protocol.  Get a copy of
the SUN RPC RFC (don't you love acronyms?), Ray Brand has it.

	In terms of name mappers: Mine is currently still under way, posting
of the current user.doc and mapperbase.h will occur in the next few days.
It could be used to prevent having inumerable different name mappers.

>--JimG

Randell Jesup			{uunet|ihnp4|allegra}!cbmvax!jesup