You're mixing up two different approaches to reading the file.
When you use fs.createReadStream(), the file will be read automatically as
a stream, and you'll start seeing 'data' events with chunks of data as
they're read. With this model, you don't do the reading, the stream does it
for you.
On the other hand, if you want to read the file manually, you'll need to
open it using fs.open() first. Then you can use fs.read() calls to get the
data.
I'd recommend the stream approach, unless there's some reason you can't do
that.
--
Martin Cooper
On Sat, Nov 10, 2012 at 12:00 PM, Volkan Yazıcı <volkan.yaz...@gmail.com>wrote:
The problem is some libraries operate on fds to consume the input partially. (E.g., consider parsing the header of a binary file. Library first makes some read()'s, and by looking at the result of those read()'s, maybe some more read()'s too, etc.) OTOH, in my case, the input is piped through some other library which provides you a stream. And I need to pipe that stream to some other library that asks for a fd. Any recommendations?
On Saturday, November 10, 2012 10:57:30 PM UTC+2, Martin Cooper wrote:
> You're mixing up two different approaches to reading the file.
> When you use fs.createReadStream(), the file will be read automatically as > a stream, and you'll start seeing 'data' events with chunks of data as > they're read. With this model, you don't do the reading, the stream does it > for you.
> On the other hand, if you want to read the file manually, you'll need to > open it using fs.open() first. Then you can use fs.read() calls to get the > data.
> I'd recommend the stream approach, unless there's some reason you can't do > that.
> --
> Martin Cooper
> On Sat, Nov 10, 2012 at 12:00 PM, Volkan Yazıcı <volkan...@gmail.com<javascript:>
> > wrote:
>> Hi! I am having trouble while *fs.read*'ing from fd of a stream. For >> instance, below script produces no outputs. What am I missing?
>> var fs = require("fs"),
>> s = fs.createReadStream(__filename),
>> l = 8192,
>> b = new Buffer(l);
