prashant roy said the following on 09/22/2009 05:16 PM: > oh yes, I got point #1. > > 2._ application level data library, so we can set data via Mach-ii > and access via Mach-ii data library_ > ---- I mean, most of the time, our application needs > big amount of data in application scope for example- all *DROP DOWN > *values, *ROLES and their assigned functionalities* data, some > *application level static data *that application don't modify on > regular basis like list of companies, list of employees or any such > data. In my last project I was not comfortable to assign these data to > UDFs, property or anything else as I consider these data as > application data and i want to store this data in application scope so > I had created *App.data* object variable to store these data on > application start. Properties are the Mach-II equivalent of the "application" scope. So I would stash them there. If you have to load them from a DB, you can write a Mach-II property CFC that makes the queries in the configure() method and then stash them in the Mach-II properties. Here's the FAQ about using scopes in Mach-II:
http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/wiki/UsingScopesInMachII#ApplicationVariables Best, .Peter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to Mach-II for CFML list. 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/mach-ii-for-coldfusion?hl=en SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/ Wiki / Documentation / Tickets: http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/ -~----------~----~----~----~------~----~------~--~---
