RE: [PHP] what PHP really needs

> > > Like Hamid Said, if the ColdFusion server has the query already in > memory. > > It doesn't need to send traffic to another server to get the information > > again. Most systems I've worked on have the db and the web server on > > different areas of a firewall, so you're going through a lot of excess > steps > > if you're hitting the db every time for something that won't change. > > You missed the point. If you have to connect to a server anyway, whjat's > the difference between going to a cached queryset on a CF server or going > to a cached queryset on a db server? It's a wire transaction in any case. [Marlon Moyer] Because most CF servers are installed on the same web server, no wire is required between the web server and cf server. > > > Plus, you have a granular control on what is being cached. The sql > server > > will only cache what it has room for. So if enough queries are run > against > > it, the original query won't be cached anymore regardless. > > And this won;t happen on the CF server when you run out of memory to cache > a transaction? Yeah, right. > [Marlon Moyer] You don't have much control over what a db server caches, but considering I can tell CF exactly what I want it to save the chances are less likely, but still possible, that it will flush from memory. It's the same with session variables. I could keep saving data in session variables until I ran out of memory also. > Does CF have to query the db server to stay in sync? Of course it does. > Now there's multiple transactions to coordinate & synchronize. > [Marlon Moyer] I'm not talking about queries that require constant refreshing. That would be a bad use of an application variable. What I'm talking about are queries that maybe refresh once or twice a day. I can schedule this easily. > > But I think the original question was about a tree that took a long time > to > > create, and application variables would be a plus in this situation..... > > That remains to be seen. Getting the data in an optimal way can be a > non-trivial operation. > > -- > "Half the people know what they're talking about, and the > other half are writing code." >