Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!rs6000.cmp.ilstu.edu!ejbehr
From: ejbehr@rs6000.cmp.ilstu.edu (Eric Behr)
Newsgroups: comp.protocols.tcp-ip
Subject: Info on directory servers requested
Message-ID: <1991Jun27.054611.4587@rs6000.cmp.ilstu.edu>
Date: 27 Jun 91 05:46:11 GMT
Reply-To: ejbehr@rs6000.cmp.ilstu.edu (Eric Behr)
Organization: Central Illinois Surfing Club
Lines: 21

I'm toying with the idea of implementing a small local (campus) directory
server on a little Unix machine (an A/UX SE/30, maybe?). It's more of an
experiment, or showing someone that it *can be done*, rather than a *real*
service.

I imagine a Unix daemon, which would respond to requests on one of the
unused ports, and search a text file database for matches. I'm interested
only in queries like <last name> {<first name>}, possibly with wildcards.
The idea is to get e-mail address(es) of the matching person(s) in return,
nothing else; the response would be handled by some simple PC front-end.

I read the RFC on DAP, and it sort of scared me by the complexity of the
protocol. It does mention a program called "dish" - hence my first
question: where can I get it? what does it do?

Second question: has anyone implemented this obvious simple scheme I
described above? Or maybe it isn't as simple as it seems to me? I'd be
grateful for all comments and hints.
-- 
Eric Behr, Illinois State University, Mathematics Department
Internet: ejbehr@rs6000.cmp.ilstu.edu    Bitnet: ebehr@ilstu