= Summary of New Features In MG3 Alpha =

[[TOC(inline)]]

== [wiki:HowTos/EventGeneration Event Generation] ==
By calling undefined events in the URL, we can tell Model-Glue to do all the needed setup and free us from having to modify the !ModelGlue.xml file directly or create the files to handle the event. All of this is done by naming convention and makes the setup process very easy.

== [wiki:HowTos/EventCopyToScope Event.copyToScope()] ==

== [wiki:HowTos/SESUrls Search Engine Safe Urls] ==
In previous versions of MG there was no built in SES URL handling.  However, it could be manually implemented using a number of techniques.  In many cases the user may or may not have been using the "myself" value which held the path to the index.cfm.  If you're using SES URL features in MG3 you won't want to use myself any more.  Instead, you'd use the event.linkto() function.

Actually, you'll want to use event.linkto inplace of self and myself now as this will allow you to switch your entire app to SES URLS quickly and easily.

== [wiki:HowTos/ApplicationCFCIntegration Application.CFC Integration] ==

== [wiki:HowTos/CachingLayer Content Caching] ==
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.  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.

== [wiki:HowTos/Helpers Helpers] ==

== [wiki:HowTos/Formats Formats] ==

== [wiki:HowTos/Remoting Remoting] ==