Complete.Org: Mailing Lists: Archives: gopher: April 2002:
[gopher] Re: Pygopherd nearing gopherd replacement
Home

[gopher] Re: Pygopherd nearing gopherd replacement

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Pygopherd nearing gopherd replacement
From: Ralph Furmaniak <sugaku@xxxxxxxxxxxx>
Date: Thu, 04 Apr 2002 18:37:05 -0500
Reply-to: gopher@xxxxxxxxxxxx

> Pygopherd also does not add
> an extra (or "second" if you're using URLs) type character like UMN
> gopherd does.  Because it figures all this out itself, that is
> unnecessary.

This does have its uses.  For example an executable must be able to return
either a plain file or a menu (gophermap format).  If you include the
character you can also do things such as using type 1 for a file and have it
read as a gophermap menu.

This character is also used to signify mail spool files.

Including the type character can make the code somewhat (albeit not much)
simpler and does not cause any problems that I am aware of.



[Prev in Thread] Current Thread [Next in Thread]