That makes sense but I can't think of many problems with shared objects other than name collisions which can be avoided with prefixed namespacing. I guess you might get into trouble if assumptions are made about a shared object such as it's ability to be serialized but making such assumptions about things that you know are shared would be pretty stupid.
I think this solution is mostly needed to avoid the smell of a kludge (props on shared objects). On Sun, Sep 8, 2013 at 9:38 PM, Forrest L Norvell <[email protected]>wrote: > The simple, short answer is that that advice is meant for module writers, > not app developers. > > The slightly longer answer is that attaching random properties onto shared > objects ends up causing all kinds of chaos when you try to combine modules. > I don't know about now, but there was a while when it was impossible to > load Restify and Express into an app at the same time, and I've seen cases > of 3rd party middleware functions doing incompatible things with req and > res. > > F > > > On Sun, Sep 8, 2013 at 9:06 PM, Mark Hahn <[email protected]> wrote: > >> From the continuation-local-storage readme: "anywhere where you might >> have set a property on the request or response objects in an HTTP handler, >> you can (and should) now use continuation-local storage". >> >> Why? I add a lot of properties to request and response objects using >> unique property-name prefixes to avoid collisions. It works fine. >> >> -- >> -- >> 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. >> > > -- > -- > 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. > -- -- 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.
