[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [gopher] parent directory



You may also be interested in the various Path parameters in caps.txt files. Gopher itself imposes no structure onto the selector, but most servers use some standard path structure and this may be exposed in the caps file if one has been set up.

On Sat, Aug 19, 2017 at 9:30 PM, James Mills <prologic@shortcircuit.net.au> wrote:
IIRC there is no standard around a "parent" item in gopehrmap(s).

It's up to the content authors.

cheers
James


On Fri, Aug 18, 2017 at 7:59 AM, Glenn Holmer <cenbe@kolabnow.com> wrote:
I'm working on a Commodore 64 gopher client and a custom server that can
send files to it from within disk images. I'm only supporting gophermap
for now, but I'm wondering how "parent directory" links on gopher pages
are implemented. Is there usually a gophermap in each directory on the
server with a gopher item pointing to the parent directory? or do
clients typically retain a stack of visited directories and items?

--
Glenn Holmer (Linux registered user #16682)
"After the vintage season came the aftermath -- and Cenbe."

_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project


_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project



--
The views expressed above are exclusively mine, if anyone's.
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project

Reply to: