What's wrong with parking database connections in a module? Most high level database libraries use a pool of connections internally and give you a simple API on top. They have effectively hidden the database connection in the module.
On Thu, Dec 6, 2012 at 8:47 PM, Forrest L Norvell <[email protected]>wrote: > If you find yourself trying to use global state, either via explicitly > global variables or by parking database connection handles in a module, > you're trying to force a solution and should probably take a step back and > think up a more naturally asynchronous strategy. > -- 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
