I laughed at the part where Mikeal says that connect doesn't deserve to exist. I agree that database connectors shouldn't be packaged (primarily) as middleware layers, but remember the reason I designed connect in the first place. There were several competing http frameworks that were duplicating the same logic over and over with zero code reuse or sharing.
So what's better? How can someone write an http-auth library that integrates with any node http server? Also what about a more generic plugin system for node in general where plugins can provide API services and consume other services? https://github.com/c9/architect On Mon, Apr 16, 2012 at 12:37 PM, NodeUp <[email protected]> wrote: > We recorded a special framework author throwdown for NodeUp with the > authors of Geddy (http://geddyjs.org), Tako (https://github.com/mikeal/ > tako), Flatiron (http://flatironjs.org) and SocketStream (https:// > github.com/socketstream/socketstream). > > If you're interested you can listen to it here, > http://nodeup.com/seventeen. > > -- > 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 > -- 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
