jonknee wrote: >> But I would really like to do it the cake way, so my question is, what >> can I do to speed it up over controller/action? And if there is not >> much I can do, how could I at least include the cakePHP database >> connection into the extra php file? >> > > The CakePHP way would be to not store the images in the database... > It's a pretty poor practice, especially in a case like yours with 20 > different images. And especially when you are working through a > framework because of the additional overhead. Think about how browsers > work, there's one request for the page and then another request for > each file required (stylesheets, JS scripts and images). In your app > just one page load is like getting over 20 simultaneous hits. That > isn't terribly bad for static content like images because they get > served up really quickly, but CakePHP has a significant overhead and > won't be able to easily scale for what you're doing. Your server is > doing 20x the work that it should be doing.
Would view caching help in this circumstance? Assuming that there is some good reason for the images to be in the database, then this should avoid most of the Cake overhead. Just a thought ... Langdon --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
