Takeshi,
See discussion here too: https://github.com/whatwg/streams/issues/33
The problem with stop again is that I need to handle myself the clone
operations, the advantage of stop-eof is:
- clone the operation
- close it
- restart from the clone
And as I mentioned before this would work
No, see my previous reply, unless I am proven incorrect, I still think
we should have:
- pause/unpause
- stop/(implicit resume)
Regards,
Aymeric
Le 11/11/2013 22:06, Takeshi Yoshino a écrit :
Aymeric,
Re: pause()/resume(),
I've moved flow control functionality for non-exact read() method
On Tue, Nov 12, 2013 at 5:23 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
No, see my previous reply, unless I am proven incorrect, I still think we
should have:
- pause/unpause
- stop/(implicit resume)
Regards,
Aymeric
Le 11/11/2013 22:06, Takeshi Yoshino a écrit :
Aymeric,
On Tue, Nov 12, 2013 at 5:20 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
Takeshi,
See discussion here too: https://github.com/whatwg/streams/issues/33
The problem with stop again is that I need to handle myself the clone
operations, the advantage of stop-eof is:
- clone the operation
Aymeric,
Re: pause()/resume(),
I've moved flow control functionality for non-exact read() method to a
separate attribute pullAmount [1] [2]. pullAmount limits the max size of
data to be read by read() method. Currently the pipe() method is specified
not to respect pullAmount but we can choose to
Please see here https://github.com/whatwg/streams/issues/33, I realized
that this would apply to operations like textDecoder too without the
need of an explicit stream option, so that's no more WebCrypto only related.
Regards
Aymeric
Le 07/11/2013 11:25, Aymeric Vitte a écrit :
Le
On Fri, Nov 8, 2013 at 5:38 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
Please see here https://github.com/whatwg/streams/issues/33, I realized
that this would apply to operations like textDecoder too without the need
of an explicit stream option, so that's no more WebCrypto only related.
Sorry. I've cut the input at wrong position.
textDecoderStream.write(arraybuffer of 0xd0 0xa0 0xd0 0xbe 0xd1 0x81 0xd1);
textDecoderStream.stop();
textDecoderStream.write(arraybuffer of 0x81 0xd0 0xb8 0xd1 0x8f)
I would expect Poc (stop, keep 0xd1 for the next data) and сия
It can be seen a bit different indeed, while with crypto you expect the
finalization of the operation since the begining (but only by computing
the latest bytes), here you can not expect the string since the begining
of course.
On Fri, Nov 8, 2013 at 8:54 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
I would expect Poc (stop, keep 0xd1 for the next data) and сия
It can be seen a bit different indeed, while with crypto you expect the
finalization of the operation since the begining (but only by computing the
latest
stop/resume:
Indeed as I mentioned this is related to WebCrypto Issue22 but I don't
think this is a unique case. Issue22 was closed because of lack of
proposals to solve it, apparently I was the only one to care about it
(but I saw recently some other messages that seem to be related), and
On Thu, Nov 7, 2013 at 6:05 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
stop/resume:
Indeed as I mentioned this is related to WebCrypto Issue22 but I don't
think this is a unique case. Issue22 was closed because of lack of
proposals to solve it, apparently I was the only one to care
Le 07/11/2013 10:21, Takeshi Yoshino a écrit :
On Thu, Nov 7, 2013 at 6:05 PM, Aymeric Vitte vitteayme...@gmail.com
mailto:vitteayme...@gmail.com wrote:
stop/resume:
Indeed as I mentioned this is related to WebCrypto Issue22 but I
don't think this is a unique case. Issue22 was
On Thu, Nov 7, 2013 at 6:27 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
Le 07/11/2013 10:21, Takeshi Yoshino a écrit :
On Thu, Nov 7, 2013 at 6:05 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
stop/resume:
Indeed as I mentioned this is related to WebCrypto Issue22 but I don't
think
Le 07/11/2013 10:42, Takeshi Yoshino a écrit :
On Thu, Nov 7, 2013 at 6:27 PM, Aymeric Vitte vitteayme...@gmail.com
mailto:vitteayme...@gmail.com wrote:
Le 07/11/2013 10:21, Takeshi Yoshino a écrit :
On Thu, Nov 7, 2013 at 6:05 PM, Aymeric Vitte
vitteayme...@gmail.com
I have seen the different bugs too, some comments:
- maybe I have missed some explaination or some obvious thing but I
don't understand very well right now the difference/use between
readable/writablebytestream and bytestream
- pause/unpause: as far as I understand the whatwg spec does not
On Wed, Nov 6, 2013 at 7:33 PM, Aymeric Vitte vitteayme...@gmail.comwrote:
I have seen the different bugs too, some comments:
- maybe I have missed some explaination or some obvious thing but I don't
understand very well right now the difference/use between
readable/writablebytestream and
FYI, I added a branch named Preview version into which suggestions are
incorporated aggressively to see how the API surface would be change.
https://dvcs.w3.org/hg/streams-api/raw-file/tip/preview.html
Please take a look if you're interested in.
For stabler version edited after having discussion,
I'd like to summarize my ideas behind this API surface since the overlap
thread is too long. We'll put these into bug entries soon.
Feedback on Overlap thread, especially Issac's exhaustive list of
considerations and conversation with Aymeric were very helpful. In reply to
his mail, I drafted my
On Tue, Nov 5, 2013 at 2:11 AM, Takeshi Yoshino tyosh...@google.com wrote:
Feedback on Overlap thread, especially Issac's exhaustive list of
considerations
Deleted citation by mistake. [1] is the Issac's post.
[1]
http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0355.html
20 matches
Mail list logo
