On 04.03.2010, at 1:52, Olli Pettay wrote:
I noticed that WebSocket spec updated to not inlcude framing
overhead in
bufferedAmount.
I asked that since from API point of view it doesn't make
much sense to have the frame bytes to be magically included in the
bufferedAmount.
What if we
On 3/5/10 7:54 PM, Alexey Proskuryakov wrote:
On 04.03.2010, at 1:52, Olli Pettay wrote:
I noticed that WebSocket spec updated to not inlcude framing overhead in
bufferedAmount.
I asked that since from API point of view it doesn't make
much sense to have the frame bytes to be magically
--
Omid Ashtari
310-346-3191
oasht...@gmail.com
@oashtari
On 05.03.2010, at 10:27, Olli Pettay wrote:
I was going to mention this as the primary reason why frame bytes
should
be included. JavaScript code needs this information for flow control,
Why?
I assume you are asking why JavaScript code needs this information for
flow control.
My
On 3/5/10 10:39 PM, Alexey Proskuryakov wrote:
On 05.03.2010, at 10:27, Olli Pettay wrote:
I was going to mention this as the primary reason why frame bytes should
be included. JavaScript code needs this information for flow control,
Why?
I assume you are asking why JavaScript code needs
On 05.03.2010, at 12:56, Olli Pettay wrote:
And you're saying that javascript really needs to know about the
frame boundary bytes to detect if it is streaming too fast.
Doesn't sound likely to me.
OK
That's true, but I don't know how many of these have already been
sent
unless I perform
On 3/5/10 11:13 PM, Alexey Proskuryakov wrote:
On 05.03.2010, at 12:56, Olli Pettay wrote:
And you're saying that javascript really needs to know about the
frame boundary bytes to detect if it is streaming too fast.
Doesn't sound likely to me.
OK
That's true, but I don't know how many of
Is this the right list for this kind of question?
2010/2/23 Mike Samuel mikesam...@gmail.com:
I'm working with EcmaScript TC39 trying to allow for experimentation
with new content generation techniques in JavaScript.
There's one missing piece which would let template language authors
On 05.03.2010, at 13:17, Olli Pettay wrote:
for something no one should care about, as you
implied above.
From API perspective I do care. Web developers shouldn't need to know
about the protocol, yet (s)he should be able to understand what
bufferedAmount means.
An explanation like it's how
