I appreciate the problem you're trying to solve, but your solution feels like a reinvention of the async module, or perhaps a promises module like "q". Yours will be fine until you need "if / while / each" logic and you have to add more and more reimplementations of features already found in those.
I'm not convinced you need to comingle the problem of routing HTTP requests with the problem of callback hell in a single library. On Tuesday, January 13, 2015 at 12:57:33 AM UTC-5, Amir Yasin wrote: > > I've written a couple of large Express apps and a few smaller ones and > invariably anything complex starts descending into callback hell. I'm > working on a solution for that and I think I'm ready at this point for some > community feedback. Bear in mind that there's a fair bit of work left to > do and it's not a 'production' project yet. Nevertheless there's enough > there to give you a sense of where I'm going with it...feedback and > constructive criticism would be greatly appreciated. > > The project is located at https://github.com/ayasin/frhttp > > Thanks > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/a2dd6156-652f-4aaf-8dfc-2c564b2bf4ae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
