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

[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: JumpJet Mailbox <jumpjetinfo@xxxxxxxxx>
Date: Thu, 10 Jul 2008 13:34:36 -0700 (PDT)
Reply-to: gopher@xxxxxxxxxxxx

Expediency is what always gets us into trouble.  Does anyone remember the Y2K 

--- On Wed, 7/9/08, Jay Nemrow <jnemrow@xxxxxxx> wrote:

From: Jay Nemrow <jnemrow@xxxxxxx>
Subject: [gopher] Re: Item Type Suggestions
To: gopher@xxxxxxxxxxxx
Date: Wednesday, July 9, 2008, 12:28 AM

Although the philosophy of all of this just gets my heart beating faster,
Cameron has the perspective of the person actually coding all of this in the
real world client!  I would just as soon have the client working smoothly as
to force it to obey a nice idea that makes coding a nightmare.  Let the
programmer win the day!
On Tue, Jul 8, 2008 at 3:25 PM, Cameron Kaiser <spectre@xxxxxxxxxxxx>

> Here's the problem with that, though: the browser thinks in MIME
> To get the proper MIME type out of a file that could be arbitrarily CSS,
> XML *or* HTML, you'd need to resort to content sniffing or extension
> grokking, which is what I want to avoid.
> I'm fully in agreement with your first paragraph, but for certain
tasks a
> 1:1 mapping is going to be unavoidable from an expediency point of view.
> At least for this specific case I cannot see a way of avoiding it.
> --
> ------------------------------------ personal:
> --
>  Cameron Kaiser * Floodgap Systems * *
> ckaiser@xxxxxxxxxxxx
> -- The only thing to fear is fearlessness -- R. E. M.
> -------------------------


[Prev in Thread] Current Thread [Next in Thread]