looks ok to me. you could take into account mountable apps explained here http://vimeo.com/56166857 so a controller can be a mounted application mounted under a certain path (resolves possible conflicts and is more reusable)
i also read the following article about authorization and thats a mess. dont monkey patch, use middleware like passportjs or everyauth and pass it with your authorization function. Am Freitag, 15. März 2013 15:25:04 UTC+1 schrieb Renato M. da Gama: > > Hi guys, I am documenting my architectural choices in a blog I am writing > with a friend. > > This is the first post I wrote, I would like to know if you can review and > give feedback in terms of coding and if possible in terms of writing. It is > aprox. 650 words > > http://ec2-54-232-84-48.sa-east-1.compute.amazonaws.com/structuring-a-node-js-web-application-with-express/ > > > > Thank you very much. > -- -- 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.
