[nodejs] Re: Simple LightWeight OOP. 100% compatibility with JavaScript. Feedback please!

2012-11-05 Thread tjholowaychuk
"without the helper, you must repetitive times write: "Name.prototype"" still looks better, and the additional context is worth it IMO, plus editors are good at dealing with repetitive tasks, at least half the code I "write" is not typed, I think the same goes lots of devs On Nov 5, 8:02 pm, Jake

Re: [nodejs] Turning Off Nagle Algorithm for HTTP Server

2012-11-05 Thread P. Douglas Reeder
Thanks! var server = http.createServer(...); server.on("connection", function (socket) { socket.setNoDelay(true); }); server.listen(port, ipAddress, callback); also works. On Monday, November 5, 2012 8:39:25 PM UTC-5, Isaac Schlueter wrote: > > I think it might've been called req.connecti

Re: [nodejs] Turning Off Nagle Algorithm for HTTP Server

2012-11-05 Thread Isaac Schlueter
I think it might've been called req.connection back then. On Mon, Nov 5, 2012 at 3:44 PM, Nathan Rajlich wrote: > req.socket.setNoDelay() > > On Mon, Nov 5, 2012 at 11:17 AM, P. Douglas Reeder > wrote: >> To tun off the Nagle algorithm on a socket server, one calls >> socket.setNoDelay([noDelay

[nodejs] Re: basecamp 2 module?

2012-11-05 Thread Mark Hahn
I'm starting my own. No choice. On Mon, Nov 5, 2012 at 1:38 PM, Mark Hahn wrote: > The only basecamp modules I've found, node-basecamp and manaslu, are for > the old basecamp api. Does anyone know of an up-to-date module? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://git

[nodejs] Sharing authentication and sessions with django

2012-11-05 Thread Timmy O'Mahony
I'm planning a single-page realtime application that I want to write in node (with express+connect+socket.io and so on). That said, I want to write the 'support code/website aspect' with django. What I mean by 'support code/website aspect' is things like: - frontpage & other static pages a

Re: [nodejs] Turning Off Nagle Algorithm for HTTP Server

2012-11-05 Thread Nathan Rajlich
req.socket.setNoDelay() On Mon, Nov 5, 2012 at 11:17 AM, P. Douglas Reeder wrote: > To tun off the Nagle algorithm on a socket server, one calls > socket.setNoDelay([noDelay]). For a client HTTP request, one calls > request.setNoDelay([noDelay]). But how does one get the socket for an HTTP > se

[nodejs] basecamp 2 module?

2012-11-05 Thread Mark Hahn
The only basecamp modules I've found, node-basecamp and manaslu, are for the old basecamp api. Does anyone know of an up-to-date module? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message becaus

[nodejs] Re: poll file descriptor in node.js

2012-11-05 Thread Henri Tuhola
Thanks from your help. Here's something back: https://github.com/cheery/node-udev sunnuntai, 4. marraskuuta 2012 0.14.01 UTC+2 Bert Belder kirjoitti: > > On Saturday, November 3, 2012 10:40:20 PM UTC+1, Henri Tuhola wrote: >> >> I want to do an event emitter that gets events from libudev. >> >> u

[nodejs] Turning Off Nagle Algorithm for HTTP Server

2012-11-05 Thread P. Douglas Reeder
To tun off the Nagle algorithm on a socket server, one calls socket.setNoDelay([noDelay]). For a client HTTP request, one calls request.setNoDelay([noDelay]). But how does one get the socket for an HTTP server, in order to call setNoDelay()? I'm restricted to using Node v0.2.3 and v0.4.12, s

[nodejs] Re: Simple LightWeight OOP. 100% compatibility with JavaScript. Feedback please!

2012-11-05 Thread Fredrik O
Den måndagen den 5:e november 2012 kl. 10:01:58 UTC+1 skrev greelgorke: > > 3. I guess "helpful" is a matter of flavor and familiarity. i don't see > the need to type down "classes" in js, may be thats the point. > 3.1 a helper in a sense of DRY have to reduce amount of code. now instead > of typ

Re: [nodejs] linking node.js with libwrap

2012-11-05 Thread Ben Noordhuis
On Mon, Nov 5, 2012 at 2:49 AM, dhruvbird wrote: > > On Sunday, November 4, 2012 5:19:40 PM UTC-5, Ben Noordhuis wrote: >> >> On Sun, Nov 4, 2012 at 10:24 PM, dhruvbird wrote: >> > Hello, >> > >> > Has anyone linked the node.js executable against libwrap so that node.js >> > based servers can mak

[nodejs] [ANN] Node-firebird version 0.1.0 released with major api changes

2012-11-05 Thread Adrian Marius Popa
Henry Gourvest announced that node-firebird version 0.1.0 is released : > I made a major update on this project. > I radically changed the api to conform to what is usually done with > node.js and databases. In particular, the error handling. Take a look on the

[nodejs] Changes in V8 GC between v0.6 and v0.8

2012-11-05 Thread Joran Dirk Greef
In case this helps anyone out: I have seen pauses of up to 22 seconds in a production application with 2GB heap data on Node v0.7 and above. I ran trace-gc and the pauses are almost all GC. The offending line is "last resort gc". It may be here in the V8 source: http://code.google.com/p/v8/s

[nodejs] V8 GC "last resort gc"

2012-11-05 Thread Joran Dirk Greef
I have been having trouble with the V8 GC taking 22 seconds. I have tried to tweak the GC flags as much as possible. Here is the thread for anyone who has similar issues: https://groups.google.com/d/topic/v8-users/Xc5EriJtpd4/discussion I went back to Node v0.6.21 which has an older V8 and this

Re: [nodejs] Memory management and tuning

2012-11-05 Thread Joel Rolfe
Thanks for the detailed explanation Vyacheslav! I've updated the post accordingly. On Saturday, November 3, 2012 2:11:41 PM UTC-7, Vyacheslav Egorov wrote: > > A lot of those flags exist solely for debugging purpose: it's > sometimes useful to switch something off and see if some issue stays

[nodejs] Re: How to use AngularJS routes with Express when a new page is requested?

2012-11-05 Thread Joel Rolfe
I have this exact stack - you don't need to worry about handling each specific possible route on the express side. Just put the entire app in a statically served directory on your node server, and set up a single route to that at the root context. app.use(_express.static("app")); My "app" dir

[nodejs] Re: Detect When USB Mass Storage Device Is Plugged In

2012-11-05 Thread Paul Spaulding
Thanks! -- 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 nodejs@googlegroups.com To unsubscr

[nodejs] Re: Detect When USB Mass Storage Device Is Plugged In

2012-11-05 Thread mscdex
On Nov 5, 9:40 am, Paul Spaulding wrote: > Using Node.js, how would I go about detecting when a USB storage device > (like a thumb-drive) is plugged into the host?  Ideally, there would be an > event that I could listen for instead of polling.  Assume a Linux OS, > although something that also wor

[nodejs] Detect When USB Mass Storage Device Is Plugged In

2012-11-05 Thread Paul Spaulding
Using Node.js, how would I go about detecting when a USB storage device (like a thumb-drive) is plugged into the host? Ideally, there would be an event that I could listen for instead of polling. Assume a Linux OS, although something that also works on Windows would be great. A pure Node.js

RE: [nodejs] Re: testing mongoose validation with vows

2012-11-05 Thread Chad Engler
I was just having this exact issue the other day, thanks for the catch Papandreou! You just saved me some serious time. -Chad From: nodejs@googlegroups.com [mailto:nodejs@googlegroups.com] On Behalf Of papandreou Sent: Monday, November 05, 2012 3:15 AM To: nodejs@googlegroups.com Subject: [

[nodejs] Re: Simple LightWeight OOP. 100% compatibility with JavaScript. Feedback please!

2012-11-05 Thread greelgorke
1. Yes, it is, but this word is overburden with a bunch of semantics and introduces the classical OO mindset immediately. But, it's your helper, name it like you wish and deal the with the consequences :) 3. I guess "helpful" is a matter of flavor and familiarity. i don't see the need to type do

[nodejs] Re: testing mongoose validation with vows

2012-11-05 Thread papandreou
It's actually a conscious design choice in vows, but I agree that it's a mistake. In the async case (last time I checked) it looks at the arity of your vow function (function.length), and if it takes less than two arguments, it assumes that you don't want the error passed to your function, just