Re: [gopher] Updated Gopher RFC

[Cameron Kaiser <spectre@floodgap.com>]

> > Exactly.  There  is only a need for a menu type, informational, interac___
> > tive (search), binary, uri (h), telnet, error  and text. The rest  could
> > be  kept  for compatibility, but for example to support the non___GIF item
> > type you have to implement heuristics anyway, which can be adopted   for
> > every  binary file.
> 
> Maybe it's a good idea to have generic purpose-based item types, that
> is, a way to say it's supposed to be viewed as an image, as a movie, a
> document, a text file, etc.
> 
> This would not be exactly as precise as a type that says "Compuserve GIF
> image" or "Portable Network Graphics", but at least tells the client
> "Hey, this is going to be an image, if you can, render it yourself or
> delegate it to your imageviewer".

We sort of have that with I (sort of), and ; and s, and (less widely
accepted) d.

-- 
------------------------------------ personal: http://www.cameronkaiser.com/ --
  Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
-- Everywhere is within walking distance if you have the time. ----------------

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