Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Mar 06, 2012 09:09 AM|LINK
urely you'd pull all the information your internal BookDTO object needs for all versions and you'd probably cache it too. The transforms would then pick and choose to populate their properties from this "master" data object.
This sounds horribly inefficient, in many cases you'd be loading data or running logic that almost no one needs. In some cases this can work fine, if the difference between versions is small (like renaming a property or changing a data type).
Ideally you want to monitor usage of resource versions over time, and only support X many, or drop support for older versions after some time.