Has there been anymore discussion of this (fs.seek) and/or implementing a position offset for readable and writeable streams as in this thread<https://groups.google.com/forum/?fromgroups=#!searchin/nodejs/fs.seek/nodejs/oMJxmMTOMg0/A4hgcSnGQjgJ>? I'm thinking of use-cases like lightweight db engines written entirely in node with the ability to do something similar to random access read/writes for performance reasons. This thread is kind of old - do methods like read and write still read data in when skipping to a position offset as mentioned below? If not it may not be an issue although being able to specify real offsets in both readable and writeable streams would allow use of existing functionality for multiple asynchronous operations rather than having to recreate this.
On Tuesday, November 15, 2011 12:45:41 PM UTC-6, Matt Sergeant wrote: > > Can I recommend node-fs-ext so you get fs.seek() at least? > > On Tue, Nov 15, 2011 at 11:12 AM, Joran Greef <[email protected]<javascript:> > > wrote: > >> Thanks Matt, it's for parsing append-only files which include meta-data >> and data. It needs to read only the meta-data and skip the data and so on. >> Files are around 100 MB each and meta-data is about 64 bytes vs data of 4 >> kilobytes per item. >> >> At the moment it's reading meta-data and data, and then skipping over the >> data in memory, but I think it may be faster to not read the data at all. >> >> >> > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
