[nodejs] Re: Node.js foundation

yep! https://www.joyent.com/about/press/joyent-moves-to-establish-nodejs-foundation https://www.joyent.com/blog/introducing-the-nodejs-foundation On Tuesday, 10 February 2015 07:43:27 UTC-5, Feb Star wrote: > > Is this true? > http://www.wired.com/2015/02/nodejs-foundation/ > -- Job board

Re: [nodejs] Re: node.js needs a new home

f paperwork and > money required. Foundations are hard. > > On Tuesday, December 3, 2013 at 10:18 AM, Laurent Fortin wrote: > > Why not a Node.js foundation? > > > https://twitter.com/mariocasciaro/status/406948487905804288 > > > > > On Tuesday, 3 December 201

[nodejs] Re: node.js needs a new home

Why not a Node.js foundation? https://twitter.com/mariocasciaro/status/406948487905804288 On Tuesday, 3 December 2013 12:24:02 UTC-5, Darren DeRidder wrote: > > Be it proposed that the community of Node.JS users and supporters will be > better served by moving the Node.JS project and its aff

[nodejs] Re: need help: readable stream "flowing mode" on Windows

gt; On Wednesday, November 20, 2013 2:03:00 PM UTC-5, Laurent Fortin wrote: >> >> Shouldn't the readable stream be in "flowing mode" after resuming? >> > > IIRC "flowing mode" is for streams2. By calling resume() here you are > switching to "old mo

[nodejs] Re: need help: readable stream "flowing mode" on Windows

ednesday, 20 November 2013 20:03:00 UTC+1, Laurent Fortin wrote: >> >> Hi, >> >> >> I am currently working on a small toolkit module for handling data >> streams (for the "streams2" API). >> https://github.com/lfortin/node-stream-tk >> >>

[nodejs] Re: need help: readable stream "flowing mode" on Windows

Also, after doing: readable.pipe( process.stdout ); the 'pipes' property inside the readable._readableState object is still === null ... On Wednesday, 20 November 2013 14:03:00 UTC-5, Laurent Fortin wrote: > > Hi, > > > I am currently working on a small toolkit

[nodejs] need help: readable stream "flowing mode" on Windows

Hi, I am currently working on a small toolkit module for handling data streams (for the "streams2" API). https://github.com/lfortin/node-stream-tk However I am getting a strange behavior on Windows. I am trying this in the REPL on the Windows platform: var readable = new stream.Readable( )

Re: [nodejs] Buffer.poolSize

Thanks for the reply Ben, that's interesting stuff. On Sunday, 18 August 2013 08:34:02 UTC-4, Ben Noordhuis wrote: > > On Sat, Aug 17, 2013 at 9:27 PM, Laurent Fortin > > wrote: > > Hi, > > > > Let's say I want to boost the SlowBuffer

[nodejs] Re: Buffer.poolSize

Thanks for the reply Trevor, and congrats for all the work done on Buffer / smalloc. On Saturday, 17 August 2013 23:48:15 UTC-4, Trevor Norris wrote: > > Performance proportionally plateaus with regard to the size of the slice. > Since the average allocation is already relatively small in compa

[nodejs] Buffer.poolSize

Hi, Let's say I want to boost the SlowBuffer size like this: // set to 1 Mb Buffer.poolSize = 1024 * 1024; Is it a good practice for boosting performance, if there is lots of memory available? -Laurent -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/

Re: [nodejs] need help with new stream API: stream.read()

Thanks Isaac, and congrats for all the work done on incoming v0.10.x ! -- -- 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 po

[nodejs] need help with new stream API: stream.read()

Hi, I am trying the new stream.Readable interface. First, I implemented a myStream._read() internal method. I am pushing data like this: myStream.push("some string"); Consuming data with myStream.read( length ) works just fine when specifying the length to read, but there is an error when n