Just a couple of cents from someone that's been passively watching
this discussion. Feel free to ignore me ;-) If we might use one word to describe Gopher, it is "simple." Gopher+ somewhat violates this, and HTTP severely violates this. MIME types have their uses, and the Web and email wouldn't work so well without them. However, even after all these years, they still aren't dealt with quite right. If you click on a file on a Web server named foo.zip and the Content-Type header says it's image/gif, what happens? And what happens after you do File -> Save in your browser, then try to open it up later? (Note: these two things are not normally the same!) Proper mailcap and MIME type handling could of course be added to Gopher. But I would ask: why? I think instead of adding more types, we could remove types and simplify. The would be:
There are existing item types in existing specs that all of the above map to. Let the client use its own mailcap, or whatever, to decide what to do with media data. -- John |
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project