This is just opinion (I am not a core developer), please take it with a grain of salt:
The framework includes the view functionality, testing it as a benchmark without the view is not a valid test (in my opinion). The only thing you are testing by doing this within a controller is to test the overhead of loading the framework itself. Excluding the view could skew this significantly. You could just create a view with "Hello World" and this would ensure you are testing the framework as it is "normally" utilized. Are you truly exploring using the framework without views? Perhaps your needs might be better served with a different solution. A framework may not be what you need. Some other questions: - If your purpose is to define overhead issues, would you include components, helpers, etc? - Will you also attempt this test with a round trip to the database? - How about attempting to somehow execute a controller method without loading the DB modules? - Where do you stop in excluding framework components before its no longer a framework? Good luck with you test, Fred Wizardry wrote: > Is it possible to have a controller that prints a simple 'Hello World' > without having an underlying index view? > > In case anyone is wondering why would I want such a thing, well I > wanted to test the performance of the CakePHP framework and wished to > know the differences in response time for the controller making a call > to the view to do an action and correspondingly doing it itself. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
