> there is another thing this would break, it would be impossible toYeah, that use case is going to be hard. If you want a tee-stream,
> stream a .read() based ReadableStream to multiple destinations...
you can implement it pretty easily on top of this. And of course, if
you use the "data" event facade, then it'll keep working just how it
does, so I don't expect existing programs to be affected too badly
until they specifically try to upgrade.
But, yes, this is a thing that's going to break in 0.9, most likely,
On Sun, Jul 29, 2012 at 10:51 AM, Bruno Jouhier <bjouh...@gmail.com> wrote:For several implementations, a read(n, cb) method is easier to do.
> Given this, I probably favor the callback style a lot more than most node
For example, on Windows, that's how we read from sockets, and on all
platforms, that's how fs.read works. So, we *must* implement
something like this for fs read streams anyway, and if we want elegant
cross-platform support, then we'll have to do that for TCP and Pipes
The ReadableStream base class will have a read([n]) method that
It will also have a _read(n, function(er, bytes)) method that you can
This makes it easy to interface with underlying systems that can only
Of course, if your system CAN safely do reads synchronously (ie, if
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.