I think it was an omission. We need to provide these methods in MG3 controllers. I would expect we'd implement this using the cache adapter, but the interface for MG2 and MG3 should remain the same.
DW On Wed, Jan 13, 2010 at 7:23 PM, Dennis Clark <[email protected]> wrote: > While researching the answer to a question posed to this list, I discovered > that the Model-Glue 2 caching functions are not present in Model-Glue 3. The > following quote is from > http://docs.model-glue.com/wiki/HowTos/HowToUseContentCaching : > > Model-Glue has historically provided some basic caching features. > Model-Glue 2 introduced a set of basic functions on the base Controller > object that allow developers to cache values for a configured period of > time. These functions are: > > *AddToCache* - This adds a named value to the cache for a period of > time. > *ExistsInCache* - This indicates if a named element exists in the > cache. > *GetFromCache* - This gets the named item from the cache. > *RemoveFromCache* - This removes a named item from the cache. > > See the API documentation for more details on these functions. > > Model-Glue 3 builds significantly on top of the caching features of > Model-Glue 2. Model-Glue 3 has a granular way to cache the outcome of event > handlers and views. However, Model-Glue 3 intentionally does not have an > object caching system. This is really a feature of your model and is not one > of Model-Glue's concerns. > > I read "Model-Glue 3 builds significantly on top of the caching features of > Model-Glue 2" to mean that Model-Glue 3 retains the previous caching > functionality and adds to it with its own caching features. However, the > rest of that paragraph implies that Model-Glue 3 caching only caches the > results of events and not values (which is the only thing the Model-Glue 2 > functions *can* cache). > > So, my question is this: was the omission of the Model-Glue 2 caching > functions from Model-Glue 3 intentional or not? If it was intentional, I'll > rephrase the above quoted section to make it clearer, add an item to the > http://docs.model-glue.com/wiki/UpgradingModelGlue/UpgradingFromModelGlue2page. > If it was not intentional, I'll file the omission in the issue > tracker. In either case the API documentation needs to be fixed as it only > documents 2 of the above 4 functions. > > Cheers, > > -- Dennis > > -- > Model-Glue Sites: > Home Page: http://www.model-glue.com > Documentation: http://docs.model-glue.com > Bug Tracker: http://bugs.model-glue.com > Blog: http://www.model-glue.com/blog > > You received this message because you are subscribed to the Google > Groups "model-glue" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<model-glue%[email protected]> > For more options, visit this group at > http://groups.google.com/group/model-glue?hl=en > -- “Come to the edge, he said. They said: We are afraid. Come to the edge, he said. They came. He pushed them and they flew.” Guillaume Apollinaire quotes
-- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en
