[nodejs] Re: How to keep node running without using Forever?

We use upstart with upstarter as our jumping-off point (it creates upstart scripts). On Monday, November 26, 2012 9:04:38 PM UTC-8, Ket wrote: > > Hi, > > I feel that I don't like Forever much to keep my app restarted when it > stopped. > > Is there an

[nodejs] Re: What happens to hook.io?

Hate to throw out a shameless plug, but we built and use a collection of modules we call Amino to accomplish some similar goals as hook.io. You can assemble a cluster of node processes (services) that communicate with each-other via pub/sub or request/reply patt

[nodejs] Re: "this" and that

> > My question was a bit "tongue in cheek." > == 'I was trolling a little bit' :) And your troll worked :) Pedro that ebook is great! I will definitely be sending a couple of our devs who are transitioning from PHP to JS there. Thanks. On Tuesday, December 11, 2012 1:46:22 PM UTC-8, spqr

[nodejs] Re: How would you do this: schedule events

Could be done in redis also, with a sorted set, where the values are json payloads of task data and the scores are timestamps. On an interval (like Jonathan suggested) you could do a query for all items older than 'now' and start processing them. On Sunday, December 16, 2012 12:12:11 PM UTC-8,

[nodejs] Re: What Editor do you use?

I use Sublime Text 2, but we have an ex-Java developer on our team who really loves Webstorm http://www.jetbrains.com/webstorm/. On Monday, December 31, 2012 7:07:23 AM UTC-8, Rodrigo Fonseca wrote: > > I'm trying to use netbeans, but when i try to put a "ejs" file, the > netbeans doesn't recog

[nodejs] Re: Convincing team to use Node

RE Hiring, I have found it difficult to find node 'pros' that are looking for a new job, however, we have started migrating some of our PHP devs (who have a little js experience) over to some node projects and they are able to become productive very quickly (a month or so). With time, they'll

Re: [nodejs] Re: Convincing team to use Node

people in the > world, that's for sure. > > > On Wed, Jan 9, 2013 at 1:15 PM, Brian Link > > wrote: > >> RE Hiring, I have found it difficult to find node 'pros' that are >> looking for a new job, however, we have started migrating some of our

[nodejs] Re: How do you release memory and control usage

Without knowing more details about your app, all I can say is you have a memory leak somewhere. V8 will garbage-collect unused memory. You'll want to survey your app for objects that grow without bounds and figure out if/how/why they should be growing like that. On Thursday, January 10, 2013 6

[nodejs] Re: How do you release memory and control usage

Also, AFAIK V8 (by default) will only eat up 1 GB of RAM, but its certainly possible your machine does not even have 1 GB. On Thursday, January 10, 2013 11:04:17 PM UTC-8, Brian Link wrote: > > Without knowing more details about your app, all I can say is you have a > memory leak somew

[nodejs] Re: multiplayer game: scaling lots of gamerooms

Not exactly the same scenario as you but we have a chat-based app that also communicates 'mood' stats every 5 seconds as well as other administrative messages. We had to build it robust enough to handle 3-5k users chatting at a pretty high frequency so we definitely needed multiple physical ma

[nodejs] Re: Does events gets executed sync'd or async'd?

I found myself wanted to use the events pattern to 'register' handlers for async-style execution. I created https://github.com/cpsubrian/node-eventflow which is just wrapper around the async module. It provides serial, parallel, waterfall, and invoke methods. I use it to great effect in comb

[nodejs] [ANN] eventflow - Add asynchronous abilities to your EventEmitters

Over the past few months I've been using this little utility module in my applications. Thought I would share it here now that it is stable and well-documented. https://github.com/cpsubrian/node-eventflow EventFlow exposes some of the great flow-control utility provided by caolan's async modu

[nodejs] Re: [ANN] eventflow - Add asynchronous abilities to your EventEmitters

Glad you find it useful. Let me know if you end up needing some of the other async methods or if anything else comes up. On Tuesday, January 15, 2013 11:08:19 AM UTC-8, leei wrote: > > Totally fills a gap for me. In the couple of cases I've needed something > like this, it is always a pain to

[nodejs] Re: [ANN] eventflow - Add asynchronous abilities to your EventEmitters

Very cool. I've been loving this pattern. Bright minds ... On Tuesday, January 15, 2013 2:35:31 PM UTC-8, Katsumoto wrote: > > I'm using the same flow for almost a year in my framework. > Here is my lightweight implementation: > https://github.com/Shogun147/Katana/blob/master/lib/bootstrap.js#L

Re: [nodejs] Re: [ANN] eventflow - Add asynchronous abilities to your EventEmitters

I think what you guys are missing is that no one said these are event emitters. They extend event emitters to provide a new pattern for register sync/async handlers. Of course if the EventEmitter object changes in core, EventFlow will have to adapt .. and thats what tests are for. > What if s

[nodejs] Re: [ANN] eventflow - Add asynchronous abilities to your EventEmitters

hat the EventEmitter object already has support for storing arrays of functions associated with a string key. So.. I'm using it :) On Monday, January 14, 2013 7:21:58 PM UTC-5, Brian Link wrote: > > Over the past few months I've been using this little utility module in my > ap

Re: [nodejs] Re: [ANN] eventflow - Add asynchronous abilities to your EventEmitters

; > If you emit a callback on an event then its bidirectional and not an event. > > By all means make a new thing but don't call it an eventemitter. > > > On Wed, Jan 16, 2013 at 10:48 PM, Brian Link > > wrote: > >> > The most important thing is that event

[nodejs] Re: Waiting for an async operation to end?

I'v been using the async module for this kind of thing. The above example could be rewritten as: ``` var fs = require('fs'); var reader = require ("buffered-reader"); var DataReader = reader.DataReader; var async = require('async'); // You kinda need to understand map-reduce concept

[nodejs] Re: New js-yaml coming soon. 20x-100x speed improvenent :)

Great new, Vitaly! We use yaml for much of our configuration and a snappier app-startup-time can't hurt. On Friday, January 18, 2013 2:34:23 AM UTC-5, Vitaly Puzrin wrote: > > I'd like to boast with rewritten js-yaml, that will be released soon. This > work was inspired by mongodb/redis drivers

[nodejs] Re: Managing physical distributed clusters

We build and use a toolkit call Amino that satisfies a number of your requirements. We also used fleet and seaport for a while, but eventually progressed towards our new approach. http://github.com/amino You'll want to look at amino-drone and amino-deploy, which can get you started deploying

[nodejs] Re: Managing physical distributed clusters

I just did a presentation at Node.DC on this very topic, so you can checkout my demos and slides. Demo-2 shows you how to launch a few drones and deploy to them. https://github.com/cpsubrian/amino-nodedc/tree/master/demos/demo-2 On Thursday, January 24, 2013 4:49:13 PM UTC-5, Brian Link wrote

[nodejs] Re: node-redis blocking question

https://github.com/carlos8f/haredis can give you pub/sub through one client and also prepares you to expand to multiple redis servers, if you ever need more redundancy. On Thursday, January 24, 2013 9:29:53 AM UTC-5, mr.hanky wrote: > > Hi, > > Is redis.subscribe() blocking? > > > Will Trigger

[nodejs] Re: Managing physical distributed clusters

Published my slides to http://cpsubrian.github.com/amino-nodedc On Thursday, January 24, 2013 4:51:52 PM UTC-5, Brian Link wrote: > > I just did a presentation at Node.DC on this very topic, so you can > checkout my demos and slides. Demo-2 shows you how to launch a few drones > a

[nodejs] Re: Managing physical distributed clusters

seems to use npm to package and request to > deployment. > > Am Donnerstag, 24. Januar 2013 23:31:46 UTC+1 schrieb Brian Link: >> >> Published my slides to http://cpsubrian.github.com/amino-nodedc >> >> On Thursday, January 24, 2013 4:51:52 PM UTC-5, Brian Link wrote:

Re: [nodejs] Re: What happens to hook.io?

I'll toss amino in here too :) http://cpsubrian.github.com/amino-nodedc/#/ https://github.com/amino/amino Has plugins for pub/sub (via redis), request/respond, and queue (via rabbitmq). On Thursday, January 31, 2013 1:59:20 PM UTC-5, Arunoda Susiripala wrote: > > hook.io tries to solve the prob

[nodejs] Re: [ANN] StrongLoop

I hope you guys find great success with your powers combined! Appreciate all you do for node core. On Thursday, February 7, 2013 2:10:11 PM UTC-8, Bert Belder wrote: > > Hello everyone, > > As you may have noticed Ben, me and a couple of other guys started a new > company called StrongLoop. We'r

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

I like the look of those functional mix-ins. Thanks for the link. On Wednesday, October 31, 2012 3:37:33 PM UTC-7, Fredrik O wrote: > > Hi everyone, > > I have just wrote a simple lightweight OOP helper and want your thoughts > about it, the implementation "Class" is only 15 lines of code, but I