Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

rjbs (4671)

rjbs
  (email not shown publicly)
http://rjbs.manxome.org/
AOL IM: RicardoJBSignes (Add Buddy, Send Message)
Yahoo! ID: RicardoSignes (Add User, Send Message)

I'm a Perl coder living in Bethlehem, PA and working Philadelphia. I'm a philosopher and theologan by training, but I was shocked to learn upon my graduation that these skills don't have many associated careers. Now I write code.

Journal of rjbs (4671)

Sunday March 20, 2005
06:47 PM

gopher

[ #23762 ]

Something got me thinking about the gopher protocol last week, and I thought it would be fun to implement something like Net::Gopher::Server. It's given me an excuse to read Network Programming with Perl, which has (so far) been quite good. I've been reading the gopher RFC and a lot of old USENET threads about Gopher+ and other extensions, too.

Since about 1996, my home page has said: "I didn't believe for a minute [in the early days of HTTP] that HTTP would replace ... Gopher."

I am now ready to admit that this was an incredibly stupid thing to believe -- not because the web was inevitable, but because gopher sucks and HTTP is much, much better. I advise anyone who wants to see a bad idea to look at RFC 1436, specifically section 3.8

Gopher is supposed to be extensible because you can add new one-character codes for new types. Types are things like "a uuencoded file" or "a CSO phone-book server" or "a tn3270 session." So, imagine that every URI schema and MIME type required its own code, and that there are only 124 available codes.

Awesome.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.