This is an issue that comes back in many domains. my view on it , is basically: the more layers of abstraction you make to interact with a resource, the more simple that interaction becomes, but also, the more generic. And thus, the less you can optimize those interactions. (well offcourse you can, but then you wouldnt use the added abstraction) Often these layers of abstraction provide some way to expose the lower-laying power (for example cake lets you define your own sql queries) but that not only circumvents the added abstractions, it also makes your app less portable.
You just have to make a compromise between RAD/portability/... and performance. imho, there is no magical solution that gives you both. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php -~----------~----~----~----~------~----~------~--~---
