Complete.Org: Mailing Lists: Archives: gopher: July 2008:
[gopher] Re: Item Type Suggestions 		Home

[gopher] Re: Item Type Suggestions

[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Item Type Suggestions
From: brian@xxxxxxxxxxxxx
Date: Tue, 8 Jul 2008 11:08:07 -0500
Reply-to: gopher@xxxxxxxxxxxx 
On Tue, Jul 08, 2008 at 09:10:52AM -0700, Cameron Kaiser wrote:
> Particularly for XML, CSS and RSS which may be hosted on a gopher server, 
> using 0 for these despite being text/* could quite possibly be seen always
> as text/plain and not further interpreted by an external viewer, which is
> probably not what we want.

Why would this type of content be suitable for a gopher server?  If I
had XML, CSS, and RSS to serve up, it certainly wouldn't be done via
gopher.

At some point, if the gopher protocol continues to become more
complex, it will gradually approach the complexity of HTTP...at which
point, the two will be indistinguishable from one another.

  --Brian
[Prev in Thread] Current Thread [Next in Thread]