/lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-August/022067.html
https://github.com/whatwg/whatwg.org · HTML · 144 lines · 72 code · 65 blank · 7 comment · 0 complexity · 03b4fa415ed7a8536a29e50ca71ccc43 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=%3C4A868700.7050105%40gmx.de%3E">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="021942.html">
- <LINK REL="Next" HREF="022068.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[whatwg] BWTP for WebSocket transfer protocol</H1>
- <!--htdig_noindex-->
- <B>Julian Reschke</B>
- <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20BWTP%20for%20WebSocket%20transfer%20protocol&In-Reply-To=%3C4A868700.7050105%40gmx.de%3E"
- TITLE="[whatwg] BWTP for WebSocket transfer protocol">julian.reschke at gmx.de
- </A><BR>
- <I>Sat Aug 15 02:59:28 PDT 2009</I>
- <P><UL>
- <LI>Previous message: <A HREF="021942.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI>Next message: <A HREF="022068.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#22067">[ date ]</a>
- <a href="thread.html#22067">[ thread ]</a>
- <a href="subject.html#22067">[ subject ]</a>
- <a href="author.html#22067">[ author ]</a>
- </LI>
- </UL>
- <HR>
- <!--/htdig_noindex-->
- <!--beginarticle-->
- <PRE>Jonas Sicking wrote:
- ><i> ...
- </I>><i> Similarly content negotiation is something I would say is even more
- </I>><i> doubtful that it has provided any value. The only site where I can
- </I>><i> remember seeing content negotiation actually used is on w3.org, an
- </I>><i> organization that is safe can be considered experts on web standards.
- </I> > ...
- google.com does use it for language selection (at least it did a few
- months ago when Ian claimed nobody was using it :-).
- Also keep in mind that Content Negotiation is widely and successfully
- used for negotiating compression (Content-Encoding: gzip) and different
- machine-to-machine formats (xml vs json).
- > ...
- ><i> However even here things immediately failed. When firefox started
- </I>><i> claiming that we supported application/xml, several urls stopped
- </I>><i> working since the browser was sent the XML file used to generate the
- </I>><i> specification, rather than something that actually usefully could be
- </I>><i> rendered.
- </I>><i> ...
- </I>
- Did it come with an XSLT PI?
- BR, Julian
- </PRE>
- <!--endarticle-->
- <!--htdig_noindex-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="021942.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI>Next message: <A HREF="022068.html">[whatwg] BWTP for WebSocket transfer protocol
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#22067">[ date ]</a>
- <a href="thread.html#22067">[ thread ]</a>
- <a href="subject.html#22067">[ subject ]</a>
- <a href="author.html#22067">[ 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>