home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.infosystems.gopher
- Path: sparky!uunet!stanford.edu!leland.Stanford.EDU!Slapshot.Stanford.EDU!schemers
- From: schemers@Slapshot.Stanford.EDU (Roland Schemers)
- Subject: Re: More bugs gopher1.1b1 (beta programmers as well as code)
- Message-ID: <1992Nov18.225223.28031@leland.Stanford.EDU>
- Sender: news@leland.Stanford.EDU (Mr News)
- Organization: Distributed Computing Group, Stanford University
- References: <mtm.722068331@CAMIS> <1edt7rINN1sl@nigel.msen.com>
- Date: Wed, 18 Nov 92 22:52:23 GMT
- Lines: 30
-
- In article <1edt7rINN1sl@nigel.msen.com>, emv@msen.com (Edward Vielmetti) |>
- |> I have a hunch that a competent perl programmer could put together a
- |> bare bones totally new server in a fairly short amount of time, either
- |> of the traditional "it's a file system" model plopped down on a bunch of
- |> directories or some kind of "it's a database" model stuck in in front
- |> of dbm or oracle or sybase databases. The protocol per se is just not
- |> that complicated.
- |>
-
- Actually I was going to do this. After thinking about the go4gw stuff, it
- seemed that a perl gopher would be much easier to write, maintain, modify,
- etc, in perl. I don't think the overhead would be that noticable, since you
- are mainly dealing with scanning files, etc, no heavy number crunching.
- Hacking the wais support and ftp gateway back in perl might not be fun :-), but they could be written in C as external go4gw type modules.
-
- Of course the builtin associative arrays combined with DBM files could be useful
- for Gopher+ and other new ideas.
-
- Sounds like a project for this weekend... :-O
-
- Roland
-
- ps. Of course the problem is once I write it someone might actually use it
- (like the go4gw stuff) :-)
-
- --
- 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
-