Hi Marco, thanks for your ideas.
> Did you consider caching at HTTP level first? Yep. I have set the following: Cache-Control: cache, store Expires: Thu, 01 Dec 1983 20:00:00 GMT Etag: 2e922b7d992758b1ee143aa70cf2ab05 Pragma: cache But with no effect. > The view manager can probably completely be replaced with a small listener > that converts `JsonModel` instances into a json http response directly. > Routing can also be simplified if you can collapse multiple routes into > smarter, custom ones. Good point! I will give this attempt a try. > ZeffMu plays quite aggressively with that: > https://github.com/BinaryKitten/ZeffMu Nice one. Will have a closer look at it, when the view manager replacement does not have much effect. > I never really bothered going lower than that. Caching is the way if it's > just simple responses without no interference (Remember to set up cache > purging correctly) A proper cache purging might be quite complicated in this case. The data returned is geographical nested set data. Purge the cache properly when one node changes is not just done by clearing the cache for all children and parent and siblings. I will try to work on a concept when all the other stuff is leading nowhere. > The view layer takes a LOT of time to run. It depends on the app, but you > should really profile it first. Yep, that was my thought in the first place, as well. Will give it a try. Thanks and best regards, Ralf -- List: [email protected] Info: http://framework.zend.com/archives Unsubscribe: [email protected]
