[nodejs] Re: Request for feedback- Yet another client-side module loader (it's different, I promise:))

This seems like a really cool idea. Here are my opinions on your questions: How to package this in a way that it can be easily used in other > projects? How can I make it integrate seamlessly with existing servers > and make it compatible with different transport mechanisms? > If you want to m

[nodejs] Re: Help with custom events emiter

Also, on an unrelated note, line 24 should really go inside a callback to .listen() as a second argument, or inside an event handler for the server's 'listening' event. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines Y

[nodejs] Re: Help with custom events emiter

On Mar 25, 10:19 pm, Edgar Veiga wrote: > I can't get why the listener declared on the cache.js file isn't making the > console.log everytime I make a request.. I'm not sure what you're expecting here. In cache.js you're creating a new instance of RequestHandler, adding a listener, and then doing

[nodejs] Help with custom events emiter

Hello guys! Can anybody please help me with this one. https://gist.github.com/2202304 I can't get why the listener declared on the cache.js file isn't making the console.log everytime I make a request.. Am I missing soming? Maybe a problem with requires :/ Best regards and thank you in advanc

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

I forgot to throw that into the script, but I have it at 512. Yea, I need to give ab a whirl. I mean do you know any performance numbers that might be reasonable for a single node process. On Mar 25, 8:52 pm, mscdex wrote: > On Mar 25, 8:50 pm, Brad Carleton wrote: > > > Do you know what kind

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

On Mar 25, 8:50 pm, Brad Carleton wrote: > Do you know what kind of performance I should be able to achieve if > everything is working correctly? It depends on the resources you have available. I have no experience with ec2 and node, so I can't really say what you should expect to see. Regarding

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

The server is pretty complex, here is the code for the load tester though, it's written in nodejs/coffeescript: Coffeescript(source): https://gist.github.com/2201903 Javascript(compiled); https://gist.github.com/2201917 Do you know what kind of performance I should be able to achieve if everythi

Re: [nodejs] recommended logging?

+1 to Winston On Sun, Mar 25, 2012 at 4:00 PM, dolphin 278 wrote: > I recommend 'winston'. https://github.com/flatiron/winston > - > Boris Egorov > skype/gtalk/nickname: dolphin278 > mobile: +7 905 728 1543 > > > > On Mon, Mar 26, 2012 at 2:34 AM, deitch wrote: > >> What do people here

Re: [nodejs] recommended logging?

I recommend 'winston'. https://github.com/flatiron/winston - Boris Egorov skype/gtalk/nickname: dolphin278 mobile: +7 905 728 1543 On Mon, Mar 26, 2012 at 2:34 AM, deitch wrote: > What do people here recommend for logging? In the old Java days, I would > use Apache commons-logging or lo

[nodejs] recommended logging?

What do people here recommend for logging? In the old Java days, I would use Apache commons-logging or log4j, sprinkle tons of log('debug',msg) statements all over the place, and raise/lower the debug level using an environment var. Of course, I much prefer turning it on to debug mode and conne

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

On Mar 25, 5:18 pm, Brad Carleton wrote: > So here at request number 699, you see the response time jump by about > 2500ms.  The "response time" is what the load tester reads and the > "time spent on server" is what the server under test reports as its > time spent on the request.  Obviously, I re

[nodejs] Re: Nodjs Performance - Concurrent Connections - Linux

Here's that table again it came out kind of weird in the original post. Request Number Response Time (ms) Server Time (ms) 696818 0 697818 0 698819

[nodejs] Nodjs Performance - Concurrent Connections - Linux

I have been working on a project for a client involving building a nodejs cluster. I am trying to get a handle on what the performance characteristics of nodejs should be. I am running the latest stable node, 0.6.13 on Ubuntu 11.10. I am running tests on Amazon EC2 with an "m1.small" and a "c1.m

[nodejs] Re: NODE_MODULE error

I figured it out. in my wscript, I should have added my "freeling_tokenizer.cc to the source array. On Mar 25, 8:44 am, rhasson wrote: > I'm writing a native module that wraps a C program.  Below is my > module declaration but when I build it with node-waf I get the > following error: > > error:

[nodejs] Re: Getting started with testing and using stubs

On Sunday, March 25, 2012 5:39:23 AM UTC+2, Rehan Iftikhar wrote: > > Hi Martin > > I was asking myself these very same questions about a year ago. What > really helped me get my head around unit testing was to read Misko > Hevery's guide to testable code: http://bit.ly/GNymAe. While the > examples

[nodejs] [ANN] view-buffer

This is a cool little tool I've been meaning to make for a while. It combines the features of Buffers, TypedArrays, and DataView into one useful interface by using Proxies to provide an amorphous surface. A ViewBuffer can start out using the same parameters as a regular Buffer, or it can wrap a

[nodejs] NODE_MODULE error

I'm writing a native module that wraps a C program. Below is my module declaration but when I build it with node-waf I get the following error: error: ‘node_module_struct’ in class ‘node’ does not name a type #define FREELING_BINDING #include #include #include "freeling_tokenizer.h" void Init

[nodejs] trying to wrap my head around "promises" - async vs Q

*Note, I am not asking which tool is better, I am simply trying to understand the differences. *I'm trying to wrap my head around promises in node. Right now I'm writing all my code in callback soup. I am researching libraries and I found async(duh) but I also f

[nodejs] Re: http.get Parse Error

On Mar 25, 1:07 am, Ed Summers wrote: > The script seems to work fine on other URLs , so I'm suspecting there > is something odd with the http server at hdl.loc.gov that is > triggering this. Possibly it's advertising http 1.1 and not actually > doing http 1.1? Any help and/or workarounds you coul

[nodejs] Re: Parsing a website with java script content on server side

On Mar 25, 2:36 am, Mark Hahn wrote: > This does what you want, but i'm not sure how you would execute it from > PHP.  You could maybe spawn a process. Well, PHP has that v8 extension now ;-) -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mail