/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

  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
  2. <HTML>
  3. <HEAD>
  4. <TITLE> [whatwg] BWTP for WebSocket transfer protocol
  5. </TITLE>
  6. <LINK REL="Index" HREF="index.html" >
  7. <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">
  8. <META NAME="robots" CONTENT="index,nofollow">
  9. <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
  10. <LINK REL="Previous" HREF="021942.html">
  11. <LINK REL="Next" HREF="022068.html">
  12. </HEAD>
  13. <BODY BGCOLOR="#ffffff">
  14. <H1>[whatwg] BWTP for WebSocket transfer protocol</H1>
  15. <!--htdig_noindex-->
  16. <B>Julian Reschke</B>
  17. <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"
  18. TITLE="[whatwg] BWTP for WebSocket transfer protocol">julian.reschke at gmx.de
  19. </A><BR>
  20. <I>Sat Aug 15 02:59:28 PDT 2009</I>
  21. <P><UL>
  22. <LI>Previous message: <A HREF="021942.html">[whatwg] BWTP for WebSocket transfer protocol
  23. </A></li>
  24. <LI>Next message: <A HREF="022068.html">[whatwg] BWTP for WebSocket transfer protocol
  25. </A></li>
  26. <LI> <B>Messages sorted by:</B>
  27. <a href="date.html#22067">[ date ]</a>
  28. <a href="thread.html#22067">[ thread ]</a>
  29. <a href="subject.html#22067">[ subject ]</a>
  30. <a href="author.html#22067">[ author ]</a>
  31. </LI>
  32. </UL>
  33. <HR>
  34. <!--/htdig_noindex-->
  35. <!--beginarticle-->
  36. <PRE>Jonas Sicking wrote:
  37. &gt;<i> ...
  38. </I>&gt;<i> Similarly content negotiation is something I would say is even more
  39. </I>&gt;<i> doubtful that it has provided any value. The only site where I can
  40. </I>&gt;<i> remember seeing content negotiation actually used is on w3.org, an
  41. </I>&gt;<i> organization that is safe can be considered experts on web standards.
  42. </I> &gt; ...
  43. google.com does use it for language selection (at least it did a few
  44. months ago when Ian claimed nobody was using it :-).
  45. Also keep in mind that Content Negotiation is widely and successfully
  46. used for negotiating compression (Content-Encoding: gzip) and different
  47. machine-to-machine formats (xml vs json).
  48. &gt; ...
  49. &gt;<i> However even here things immediately failed. When firefox started
  50. </I>&gt;<i> claiming that we supported application/xml, several urls stopped
  51. </I>&gt;<i> working since the browser was sent the XML file used to generate the
  52. </I>&gt;<i> specification, rather than something that actually usefully could be
  53. </I>&gt;<i> rendered.
  54. </I>&gt;<i> ...
  55. </I>
  56. Did it come with an XSLT PI?
  57. BR, Julian
  58. </PRE>
  59. <!--endarticle-->
  60. <!--htdig_noindex-->
  61. <HR>
  62. <P><UL>
  63. <!--threads-->
  64. <LI>Previous message: <A HREF="021942.html">[whatwg] BWTP for WebSocket transfer protocol
  65. </A></li>
  66. <LI>Next message: <A HREF="022068.html">[whatwg] BWTP for WebSocket transfer protocol
  67. </A></li>
  68. <LI> <B>Messages sorted by:</B>
  69. <a href="date.html#22067">[ date ]</a>
  70. <a href="thread.html#22067">[ thread ]</a>
  71. <a href="subject.html#22067">[ subject ]</a>
  72. <a href="author.html#22067">[ author ]</a>
  73. </LI>
  74. </UL>
  75. <hr>
  76. <a href="http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org">More information about the whatwg
  77. mailing list</a><br>
  78. <!--/htdig_noindex-->
  79. </body></html>