/lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-August/021942.html
https://github.com/whatwg/whatwg.org · HTML · 236 lines · 70 code · 159 blank · 7 comment · 0 complexity · 82eb77c4098a05b264952511f2a2e41c MD5 · raw file
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
- <HTML>
- <HEAD>
- <TITLE> [whatwg] BWTP for WebSocket transfer protocol
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20BWTP%20for%20WebSocket%20transfer%20protocol&In-Reply-To=%3C26b395e60908120243i679e21eco357a72dad1bbe348%40mail.gmail.com%3E">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="021943.html">
- <LINK REL="Next" HREF="022067.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[whatwg] BWTP for WebSocket transfer protocol</H1>
- <!--htdig_noindex-->
- <B>timeless</B>
- <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20BWTP%20for%20WebSocket%20transfer%20protocol&In-Reply-To=%3C26b395e60908120243i679e21eco357a72dad1bbe348%40mail.gmail.com%3E"
- TITLE="[whatwg] BWTP for WebSocket transfer protocol">timeless at gmail.com
- </A><BR>
- <I>Wed Aug 12 02:43:51 PDT 2009</I>
- <P><UL>
- <LI>Previous message: <A HREF="021943.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI>Next message: <A HREF="022067.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#21942">[ date ]</a>
- <a href="thread.html#21942">[ thread ]</a>
- <a href="subject.html#21942">[ subject ]</a>
- <a href="author.html#21942">[ author ]</a>
- </LI>
- </UL>
- <HR>
- <!--/htdig_noindex-->
- <!--beginarticle-->
- <PRE>Jonas Sicking wrote:
- ><i> The only site where I can
- </I>><i> remember seeing content negotiation actually used is on w3.org
- </I>
- fwiw, MXR (and even LXR) uses some content negotiation, and it
- generally "magically works". OTOH it's transparent, so you shouldn't
- "see" it :).
- But yes, I'd say that content negotiation is a failure. Another
- failure in that area is Link: :).
- The problem with content types i think stems more from:
- 1. images generally having random file extensions because users didn't
- understand them
- 2. users who were publishing content in other formats not actually
- having enough easy control over their hosting providers to specify the
- content type, or knowing that it was necessary
- Partially, both of these stem from the internet mantra: be strict in
- what you send and graceful in what you receive.
- However, only computers can be strict in what they send. So "be
- ignorant of what you send" + "be graceful in what you receive" results
- in "no one can trust what is sent".
- </PRE>
- <!--endarticle-->
- <!--htdig_noindex-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="021943.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI>Next message: <A HREF="022067.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#21942">[ date ]</a>
- <a href="thread.html#21942">[ thread ]</a>
- <a href="subject.html#21942">[ subject ]</a>
- <a href="author.html#21942">[ author ]</a>
- </LI>
- </UL>
- <hr>
- <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
- mailing list</a><br>
- <!--/htdig_noindex-->
- </body></html>