![(please configure the [header_logo] section in trac.ini)](/ModelGlue.com/trac.cgi/chrome/site/your_project_logo.png){kind=logo}
Changes between Version 13 and Version 14 of NewFeaturesInMG3
- Timestamp:
- 05/21/09 10:59:32 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NewFeaturesInMG3
v13 v14 1 2 3 1 = New Features In MG3 = 4 2 … … 6 4 7 5 == Bean Injection == 8 Automatically inject model components that are managed by ColdSpring into the application's controllers.6 Automatically inject model components that are managed by !ColdSpring into the application's controllers. 9 7 10 8 [wiki:HowTos/HowToUseBeanInjection How To Use Bean Injection] … … 24 22 25 23 == Search Engine Safe Urls == 26 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.24 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. 27 25 28 Actually, you'll want to use event.linkto in place of self and myself now as this will allow you to switch your entire app to SES URLS quickly and easily.26 Actually, you'll want to use event.linkto in place of self and myself now as this will allow you to switch your entire app to SES URLS quickly and easily. 29 27 30 28 [wiki:HowTos/SESUrls How To Use Search Engine Safe Urls] … … 34 32 35 33 == Content Caching == 36 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.34 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. 37 35 38 36 [wiki:HowTos/CachingLayer How To Use Content Caching] … … 46 44 == Formats == 47 45 48 Often web sites are built for multiple front-end clients. One site may serve up pages to web browser, mobile devices, Flex or AIR applications, or AJAX requests. Typically all of these clients all want the exact same data, but each will need to format the data slightly different. In the past, Model-Glue would typically require you to build multiple events to serve different flavored data results. Or one event was used and the Controller fired a different result based on the other parameters.46 Often web sites are built for multiple front-end clients. One site may serve up pages to web browser, mobile devices, Flex or AIR applications, or AJAX requests. Typically these clients all want the exact same data, but each will need to format the data in a slightly different manner. In the past, Model-Glue would typically require you to build multiple events to serve different flavored data results, or one event was used and the Controller fired a different result based on the other parameters. 49 47 50 48 Model-Glue 3 formalizes this with a new requestFormat attribute. The requestFormat attribute is now a special value in the Event context. Both the <results> and <include> tag now support a Format attribute. If specified, the result/include will only be executed if the request format value matches. … … 52 50 [wiki:HowTos/Formats How To Use Formats] 53 51 54 55 56 52 == Remoting == 57 Make use of the binary protocol AMF and the FlashRemoting gateway in MG3!53 Make use of the binary protocol AMF and the !FlashRemoting gateway in MG3! 58 54 59 55 [wiki:HowTos/Remoting How To Use Remoting] 60 61
