home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: alt.gopher
- Path: sparky!uunet!stanford.edu!leland.Stanford.EDU!schemers
- From: schemers@leland.Stanford.EDU (Roland Schemers)
- Subject: Re: Wish List Re: gopher<->NNTP et al.
- Message-ID: <1992Jul30.002659.17260@leland.Stanford.EDU>
- Sender: news@leland.Stanford.EDU (Mr News)
- Organization: Distributed Computing Group, Stanford University
- References: <1992Jul25.001230.21597@leland.Stanford.EDU> <1992Jul25.002513.22566@leland.Stanford.EDU> <Bs687G.8Cp@knot.ccs.queensu.ca>
- Date: Thu, 30 Jul 92 00:26:59 GMT
- Lines: 31
-
- In article <Bs687G.8Cp@knot.ccs.queensu.ca> hooper@ccs.QueensU.CA (Andy Hooper) writes:
- >All these gopher<->xyz gateway scripts are really neat, but they're
- >proliferating like crazy. A single, table driven, gopher gateway daemon
- >would be nice, to pull them back under some kind of umbrella something
- >like inetd does for TCP/IP daemons.
- >
-
- Of course. What I'm doing right now is trying to fill the empty space
- in our gopherspace to show management what can be done with gopher, thats
- why I've been whipping out these little gopher gateways. :-) I had already
- planned on bringing some of them together. Basically the first word in
- the selector string would be the switch:
-
- webster default SPELL gopher
- nntp ls alt.gopher
- whois schemers
-
- Then the "master" gopher gateway perl script would check which gateway
- was being called. The master gopher gateway could either be written
- like inetd and fork off the real gateway, passing it the arguments,
- or have all the smaller gateways builtin to it.
-
- Roland
-
-
-
- --
- Roland J. Schemers III | Networking Systems
- Systems Programmer | 168 Pine Hall (415)-723-6740
- Distributed Computing Group | Stanford, CA 94305-4122
- Stanford University | schemers@Slapshot.Stanford.EDU
-