453
** About QuIX in Gopherspace **

Basically, I have gone back to working with Zope in webspace.
I did this because I have always had the possibilities of 
subdomains set up for quix.us and Zope gives me a stupid-easy
way of working with them.  So, some effort is going into the 
web side and I really don't know how much effort will be 
invested in the Gopher side.

There are two roads I would like to explore:  either making
a version of pygopherd that works with subdomains, or
making a gopher server for Zope.  Personally, I think the
pygopherd idea is better, since many Zope objects don't lend
themselves to gopherspace, and everything in a gopher can be
rendered already in a http server with little change.

I would like to bascially walk away from the UMN-formatting
scheme for creating menus since it is so kludgy.  If there
was some logical way to include metadata of a sort, I would
like to go that way.  Unfortunately, Gopher is a slave to the
filesystem and unless Linux or BSD gets a good filesystem that
includes metadata, I don't think it is a good match for Gopher.

Something to ponder....
0