/lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-March/025557.html
https://github.com/whatwg/whatwg.org · HTML · 85 lines · 68 code · 10 blank · 7 comment · 0 complexity · 5b08e2d07373f01ef26891c482cc73a5 MD5 · raw file
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
- <HTML>
- <HEAD>
- <TITLE> [whatwg] WebSocket bufferedAmount includes overhead or not.
- </TITLE>
- <LINK REL="Index" HREF="index.html" >
- <LINK REL="made" HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20bufferedAmount%20includes%20overhead%20or%20not.&In-Reply-To=%3C9F539841-2652-4B5A-BAE2-B681100BBEBA%40webkit.org%3E">
- <META NAME="robots" CONTENT="index,nofollow">
- <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
- <LINK REL="Previous" HREF="025425.html">
- <LINK REL="Next" HREF="025600.html">
- </HEAD>
- <BODY BGCOLOR="#ffffff">
- <H1>[whatwg] WebSocket bufferedAmount includes overhead or not.</H1>
- <!--htdig_noindex-->
- <B>Alexey Proskuryakov</B>
- <A HREF="mailto:whatwg%40lists.whatwg.org?Subject=Re%3A%20%5Bwhatwg%5D%20WebSocket%20bufferedAmount%20includes%20overhead%20or%20not.&In-Reply-To=%3C9F539841-2652-4B5A-BAE2-B681100BBEBA%40webkit.org%3E"
- TITLE="[whatwg] WebSocket bufferedAmount includes overhead or not.">ap at webkit.org
- </A><BR>
- <I>Wed Mar 17 17:15:32 PDT 2010</I>
- <P><UL>
- <LI>Previous message: <A HREF="025425.html">[whatwg] WebSocket bufferedAmount includes overhead or not.
- </A></li>
- <LI>Next message: <A HREF="025600.html">[whatwg] WebSocket bufferedAmount includes overhead or not.
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#25557">[ date ]</a>
- <a href="thread.html#25557">[ thread ]</a>
- <a href="subject.html#25557">[ subject ]</a>
- <a href="author.html#25557">[ author ]</a>
- </LI>
- </UL>
- <HR>
- <!--/htdig_noindex-->
- <!--beginarticle-->
- <PRE>
- On 05.03.2010, at 15:32, Alexey Proskuryakov wrote:
- >>><i> for something no one should care about, as you
- </I>>>><i> implied above.
- </I>>><i> From API perspective I do care. Web developers shouldn't need to know
- </I>>><i> about the protocol, yet (s)he should be able to understand what
- </I>>><i> bufferedAmount means.
- </I>><i>
- </I>><i> An explanation like "it's how much data is buffered to be sent over
- </I>><i> network" seems adequate to me.
- </I>
- We have a suggested patch that implements the proposed new behavior
- for WebKit now, but I think that it adds unnecessary complexity, and
- puts limits on how we can refactor the code in the future. We need to
- remember frame boundaries for much longer, making it difficult to
- interface with general purpose networking code.
- I'd prefer sticking to the previously specified behavior.
- - WBR, Alexey Proskuryakov
- </PRE>
- <!--endarticle-->
- <!--htdig_noindex-->
- <HR>
- <P><UL>
- <!--threads-->
- <LI>Previous message: <A HREF="025425.html">[whatwg] WebSocket bufferedAmount includes overhead or not.
- </A></li>
- <LI>Next message: <A HREF="025600.html">[whatwg] WebSocket bufferedAmount includes overhead or not.
- </A></li>
- <LI> <B>Messages sorted by:</B>
- <a href="date.html#25557">[ date ]</a>
- <a href="thread.html#25557">[ thread ]</a>
- <a href="subject.html#25557">[ subject ]</a>
- <a href="author.html#25557">[ 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>