[nodejs] Unclosed connections to CouchDB using Cradle

Folks, I have set up an application using Cradle 0.6.4 connected to CouchDB 1.2.0, and started stress testing it... and encountered an issue. After setting up a simulated load -using nodeload- of 60 users each requesting 100 documents of about 60MB (they vary from a few bytes to 60MB, but mos

[nodejs] Re: I finished some important JS Specifications, welcome to discuss...

You can seriously compare these two files:component.json and manifest.json. JBS does not directly allow load JS file or the CSS file by "manifest.json", but you can load these other non-standard class files by the definition of class on JCS. Of course, I can allow JBS to do so, but this is not

Re: [nodejs] Re: why fallocate is not exposed?

On Sun, Feb 24, 2013 at 11:00 PM, Marcel Laverdet wrote: > others. Really this is something that might just be better off in fs-ext > (which I'm already using for flock) if you can't emulate it in Windows. To be clear, it's not just Windows. fallocate() is a _Linux-ism_. The nearest thing on ot

Re: [nodejs] Re: why fallocate is not exposed?

> Sorry if I was unclear but I'm asking about specific use cases, i.e. what are _you_ going to use it for? I think this is one of those cases where the potential uses are actually fairly clear and non-theoretical. For instance, I built a quick & dirty version of Facebook's Haystack service in Node

Re: [nodejs] NPM Readme vs Github Readme

Not that I disagree with Isaacs, but regardless of what you use for your module and regardless if you prebuild before pushing it or your module depends on coffescript (i dont suggest this), it seems important to me that you document it with javascript examples so you can reach a bigger audience bec

[nodejs] Re: NPM Readme vs Github Readme

On Feb 24, 12:05 pm, Isaac Schlueter wrote: > Example code should be in JavaScript because CoffeeScript packages > should be prebuilt and published as JavaScript.  That is the lingua > franca of the web, and the language of Node.js. +1 -- -- Job Board: http://jobs.nodejs.org/ Posting guide

[nodejs] Re: Any way to wrap http.serverResponse?

That is very similar to what I ended up doing. I wasn't quite trying to hijack, but similar. Wish I had seen it before. :-) Thanks for posting. On Sunday, February 24, 2013 12:00:54 PM UTC+2, papandreou wrote: > > Hi Deitch, > > Take a look at https://github.com/papandreou/express-hijackresponse

Re: [nodejs] NPM Readme vs Github Readme

That being said, npm-www uses https://github.com/chjj/marked/issues so send any pull reqs there. On Sun, Feb 24, 2013 at 9:05 AM, Isaac Schlueter wrote: > We only highlight JavaScript code correctly on the website. I'd like > to just not automatically highlight any other language, actually. > (T

Re: [nodejs] NPM Readme vs Github Readme

We only highlight JavaScript code correctly on the website. I'd like to just not automatically highlight any other language, actually. (There are often command line examples or output samples that get highlighted strangely.) Example code should be in JavaScript because CoffeeScript packages shoul

Re: [nodejs] announcing browserify v2

> Ouch. I guess I will have to live with the old version until new add-ons support --watch and coffee-script. +1 > Custom require extensions are gone. Sad news, I liked the way how require *.coffee or *.mustache files works seamlesly as if ti's just *.js files. -- -- Job Board: http://jobs.n

[nodejs] Re: Is there a lib to parse IRI(rfc3987)?

My 'rdf' module contains an IRI parser, rdf.IRI. It uses standard URI/IRI vocabulary terms. I haven't gotten to checking that it's fully compliant with the RFC in detecting errors, or that offers all the functionality you want, can you offer some examples?

[nodejs] Re: Any way to wrap http.serverResponse?

Hi Deitch, Take a look at https://github.com/papandreou/express-hijackresponse I haven't tried it in this exact setting, but I think it might work, even without Express. Best regards, Andreas Lind Petersen (papandreou) On Wednesday, February 20, 2013 9:05:35 PM UTC+1, deitch wrote: > > Yeah, I