[gopher] Re: PyGopherd and Gopher+
By the way, I think a nice extension of basic gopher protocol is
implemented in GN gopher server - I have just installed it on local
machine yesterday, played with it for a while and have been very
satisfied - a compact ( about 50Kb binary) and fast server with all the
features of UMN gopherd (except gopher+) and a "gophery" way of adding
extended features - by adding some extra item types (transparently for
the client) - like 7g for embedded grep-like search, 1m for "structured
files" presented as directories (as mailbox files), 0h if a HTML version
of a file is provided (something like +VIEWS), 7w, 7wc, 7wh etc.
for different types of wais
searches etc.
On Sun, Jan 01, 2006 at 09:24:54AM -0800, Cameron Kaiser wrote:
> > I think gopher+ stinks anyway. Instead of opening a new connection to
> > fetch the new (mostly undefined) attributes it would have been easier to
> > keep reserving extra tabspaces in the menus for simple things like
> > mimetype and filesize. My reason for not adding gopher+ to GopherJ is
> > that it doesn't compliment the original protocol. And as Mr. Goerzen
> > said, it's not very gophery.
>
> I agree. I would have much preferred simply extending the tabspaces. Even
> ASK-type blocks could be emulated in some fashion with this.
>
> --
> --------------------------------- personal: http://www.armory.com/~spectre/ ---
> Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
> -- Look busy. Jesus is coming soon. -------------------------------------------
>
>
--
Yours, etc.
Roman A. Pavlov
gopher://sdf.lonestar.org/1/users/rp
Reply to: