On Apr 17, 2013, at 10:06 AM, Matteo Collina <[email protected]> wrote:
> Hi Kevin, > > I have written a similar module (https://github.com/mcollina/kanban) for > pipeline-processing. > However our concern was about reducing parallelism of spawned processes. > From the read me: > <snip> > Your API seems a lot nicer than mine, but the usage should be quite similar > at least in the basic example. > > Limiting the concurrency is something you might be interested into? > > Cheers, > > Matteo Hey Matteo, I dig the Kanban metaphor with the limited work in progress. Now that I see this, it occurs to me that Streams have characteristics of Lean principles (pull-based system, signals when to pause and when to resume). Interesting. I'm not too keen on putting limited WIP measures into Pipeworks, but it's certainly something one could build on top of it. (In fact, you could probably refactor your kanban project to use it if there's any benefit). Here's a naive limited WIP system with pipeworks (to throttle my daily food intake): https://gist.github.com/kevinswiber/5406705 Cheers, -- Kevin Swiber @kevinswiber https://github.com/kevinswiber -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
