RE: [PHP] what PHP really needs

2004-01-25 Thread electroteque
A database server by nature must assume that all data is equally mutable. An application developer, however, knows by design how fresh any one piece of data needs to be and can cache accordingly. E.g., don't hit the database for your site's navigational structure or news articles every single

Re: [PHP] what PHP really needs

2004-01-25 Thread rouvas
On Friday 23 January 2004 22:33, John W. Holmes wrote: From: Chris Boget [EMAIL PROTECTED] [snip] [/snip] Learn and use C++ Or sessions. Along with serialize() and deserialize(), all are your friends in this case. He's talking about the same set of data being available

RE: [PHP] what PHP really needs

2004-01-24 Thread Mark Charette
-Original Message- From: Hamid Hossain [mailto:[EMAIL PROTECTED] As a ColdFusion Certified Developer I can say: You are right! In CF you can fire a sql statment and store its result in a variable which is not going to be removed from the server's memory after responding to the

RE: [PHP] what PHP really needs

2004-01-24 Thread Marlon Moyer
PROTECTED] Subject: RE: [PHP] what PHP really needs -Original Message- From: Hamid Hossain [mailto:[EMAIL PROTECTED] As a ColdFusion Certified Developer I can say: You are right! In CF you can fire a sql statment and store its result in a variable which is not going

Re: [PHP] what PHP really needs

2004-01-24 Thread John Nichel
Marlon Moyer wrote: 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

RE: [PHP] what PHP really needs

2004-01-24 Thread Mark Charette
On Sat, 24 Jan 2004, Marlon Moyer wrote: 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

Re: [PHP] what PHP really needs

2004-01-24 Thread John W. Holmes
Marlon Moyer wrote: 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. Again, if you're just talking about reading, how hard is it to just do this to save: $save_data = '?php $array = ' .

RE: [PHP] what PHP really needs

2004-01-24 Thread Marlon Moyer
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

RE: [PHP] what PHP really needs

2004-01-24 Thread Marlon Moyer
I don't have a problem with this method. It would be nice though to be able just set 1 application variable and be done with it. -Original Message- From: John W. Holmes Marlon Moyer wrote: But I think the original question was about a tree that took a long time to create,

RE: [PHP] what PHP really needs

2004-01-24 Thread Marlon Moyer
-Original Message- From: John Nichel [mailto:[EMAIL PROTECTED] The problem I have with this is where the database DOES change, and not on any set interval. I used to work at Insight, and our product database changed constantly, at any give moment to account for pricing

RE: [PHP] what PHP really needs

2004-01-24 Thread Mark Charette
f stock, etc. [Marlon Moyer] This isn't a situation that you would use a cached query. You would only use it when something doesn't change that often, or you have control of when it changes. Hell, I have stuff like that - it's called generate an include file with a cron job. Trivial. All

RE: [PHP] what PHP really needs

2004-01-24 Thread Mike Migurski
Let the db server handle query/cache consistency ... why put yet another server in the way that will have to be triggered by the underlying db to clear ITS cache? Very true, but tests I've done in the past with PostgreSQL and MySQL-driven PHP sites show that adding a simple static file cache (for

RE: [PHP] what PHP really needs

2004-01-24 Thread Chris Shiflett
--- Mark Charette [EMAIL PROTECTED] wrote: And only the smallest shops would consider having a web server and CF (or db) server on the same box. No scalability or easy recovery from failure. This is incorrect. The recommended Web architecture for ColdFusion is to have the Web server and the CF

Re: [PHP] what PHP really needs

2004-01-24 Thread Chris Shiflett
--- John W. Holmes [EMAIL PROTECTED] wrote: Marlon Moyer wrote: 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... Again, if you're just talking about reading, how hard is it to just do this

Re: [PHP] what PHP really needs

2004-01-24 Thread John Nichel
Chris Shiflett wrote: snip As for the ColdFusion versus PHP discussion, I'm not really interested. What about a Godzilla versus the Shrek dragon discussion? ;) -- By-Tor.com It's all about the Rush http://www.by-tor.com -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit:

[PHP] what PHP really needs

2004-01-23 Thread PHP general
There's 1 really important thing missing in PHP as I see it, and it's the ability to keep variables in memory for as long as the programmer choose. If this was possible there could be some truly great optimizations done. Some things are very slow to create but very fast to work with. I wrote a XML

RE: [PHP] what PHP really needs

2004-01-23 Thread Jay Blanchard
[snip] [/snip] Learn and use C++ -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] what PHP really needs

2004-01-23 Thread Chris Boget
[snip] [/snip] Learn and use C++ Or sessions. Along with serialize() and deserialize(), all are your friends in this case. Chris -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php

Re: [PHP] what PHP really needs

2004-01-23 Thread Ray Hunter
You can use shared memory too...only on *nix flavors though. -- Ray On Fri, 2004-01-23 at 12:42, PHP general wrote: There's 1 really important thing missing in PHP as I see it, and it's the ability to keep variables in memory for as long as the programmer choose. If this was possible there

Re: [PHP] what PHP really needs

2004-01-23 Thread John Nichel
On Fri, 2004-01-23 at 12:42, PHP general wrote: There's 1 really important thing missing in PHP as I see it, and it's the ability to keep variables in memory for as long as the programmer choose. If this was possible there could be some truly great optimizations done. Some things are very

Re: [PHP] what PHP really needs

2004-01-23 Thread Mike Migurski
There's 1 really important thing missing in PHP as I see it, and it's the ability to keep variables in memory for as long as the programmer choose. If this was possible there could be some truly great optimizations done. Some things are very slow to create but very fast to work with. I wrote

Re: [PHP] what PHP really needs

2004-01-23 Thread John W. Holmes
From: Chris Boget [EMAIL PROTECTED] [snip] [/snip] Learn and use C++ Or sessions. Along with serialize() and deserialize(), all are your friends in this case. He's talking about the same set of data being available to all instances of PHP, though. I think they're called Application

RE: [PHP] what PHP really needs

2004-01-23 Thread Marlon Moyer
-Original Message- From: PHP general Sent: Friday, January 23, 2004 1:43 PM To: [EMAIL PROTECTED] Subject: [PHP] what PHP really needs I've heard there's a feature like this in Cold Fusion, which every Cold Fusion user seems to think of as the holy grail, and I would have

Re: [PHP] what PHP really needs

2004-01-23 Thread Chris Shiflett
--- John W. Holmes [EMAIL PROTECTED] wrote: He's talking about the same set of data being available to all instances of PHP, though. I think they're called Application Variables. Yes, this is what he was talking about, which I think most people seem to have misunderstood to be something else.

Re: [PHP] what PHP really needs

2004-01-23 Thread Ryan A
Hey, I'm not really sure and am possibly wa off base but...cant something like this also be done by using global for variables? Cheers, -Ryan On 1/23/2004 9:33:55 PM, John W. Holmes ([EMAIL PROTECTED]) wrote: From: Chris Boget [EMAIL PROTECTED] [snip] [/snip] Learn and use C++

Re: [PHP] what PHP really needs

2004-01-23 Thread Chris Boget
I'm not really sure and am possibly wa off base but...cant something like this also be done by using global for variables? No, not really. That wouldn't be accessable by all users, which, as it turns out, is what the OP had asked for. Chris -- PHP General Mailing List

Re: [PHP] what PHP really needs

2004-01-23 Thread Justin Patrin
John W. Holmes wrote: From: Chris Boget [EMAIL PROTECTED] [snip] [/snip] Learn and use C++ Or sessions. Along with serialize() and deserialize(), all are your friends in this case. He's talking about the same set of data being available to all instances of PHP, though. I think they're

Re: [PHP] what PHP really needs

2004-01-23 Thread John W. Holmes
Justin Patrin wrote: Then you could use a serialized file in the filesystem that any app can read. For added speed, make a RAM-disk and store the file there. Slight overhead deserializing, but it's likely faster than recreating whatever it is (if it's large). Then you've still got to worry

Re: [PHP] what PHP really needs

2004-01-23 Thread Jason Sheets
Chris Boget wrote: I'm not really sure and am possibly wa off base but...cant something like this also be done by using global for variables? No, not really. That wouldn't be accessable by all users, which, as it turns out, is what the OP had asked for. Chris Like someone else

RE: [PHP] what PHP really needs

2004-01-23 Thread Hamid Hossain
Follows From: PHP general [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [PHP] what PHP really needs Date: Fri, 23 Jan 2004 20:42:59 +0100 There's 1 really important thing missing in PHP as I see it, and it's the ability to keep variables in memory for as long as the programmer choose