Hi Timothy, This is a recurring topic on the node.js mailing list. You'll find a lot of information (and hot debates) on http://groups.google.com/group/nodejs
My own contribution: https://github.com/Sage/streamlinejs and the blog post that I wrote about it last January: http://bjouhier.wordpress.com/2011/01/09/asynchronous-javascript-the-tale-of-harry/ node-fibers (https://github.com/laverdet/node-fibers) is another approach that leads to similar code but with a very different implementation under the hood. Bruno On Nov 10, 8:10 pm, "Timothy J. Warren" <[email protected]> wrote: > I'm trying to create a framework along the lines of CodeIgniter for PHP in > Node JS. > > I have a very, very basic start here:https://github.com/aviat4ion/JSIgnite/ > > I've noticed that callbacks very quickly become burdensome when trying to > keep the "system" or "core" part of the framework separate from the > "application" part of the framework. > > Based on what I have, what are some better ways to structure javascript on > the server side, while keeping things asynchronous? -- To view archived discussions from the original JSMentors Mailman list: http://www.mail-archive.com/[email protected]/ To search via a non-Google archive, visit here: http://www.mail-archive.com/[email protected]/ To unsubscribe from this group, send email to [email protected]
