On Dec 14, 2007, at 3:45 PM, Perrin Harkins wrote: > On Dec 14, 2007 3:04 PM, Steven Saner <[EMAIL PROTECTED]> wrote: >> Don't you have a reference to the MasonX::WebApp object defined as a >> global variable, $app or whatever? You could store the data in that >> object. > > Is there any advantage you know of to using something like > $app->data() over $m->notes()?
I honestly have never used $m->notes() so I don't know. I don't know what your data looks like, but something that I would possibly do is create a class that stores the data, and then either pass a reference to an object of said class to each component, or store it in the MasonX::WebApp object, to be accessible to each component. To me that is a cleaner interface to a chunk of data than just a straight hash or whatever. And if you then need some routines to modify or manipulate the data you can implement them as methods in the class that can be called from wherever you need to. Probably overkill if you you are only talking about a couple values though. Steve -- --------------------------------------------------------------- Steven Saner [EMAIL PROTECTED] ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Mason-users mailing list Mason-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mason-users
