Re: Re: php sometimes doesn't parses...

> Zak, Mark, > > I currently have my machine here doing a million iterations with php 404pl1 > just using > the apache benchmark. the other option might be to make a shell script that > runs lynx > with the correct URL a set number of times but this seems far better and > easier to me > I would like to see how you think this DB thing might work.. > > Cheers, > > James I'll polish up my codebase this evening, and try to send it out by the end of today. I have a previous commitment this afternoon, but I'll jump on this when I return. In essence, I use CGI PHP to hit the webserver running PHP. That way you don't use the webserver to test itself, and we "eat our own dogfood" to do testing. Inside of a for() loop, the CGI script hits to the webserver over and over and over again (exact number determined in a variable at runtime), and stores each result in a database (my example uses MySQL, but is easily abstracted). Once completed, the simple MySQL query: select distinct content from parse-test; And we see how many answers we really got. Properly functioning servers should show one line (though that must be checked, as that one line could be UNparsed code), intermittent parsing errors alone should show 2 (true answer, and unparsed code), and more serious problems than we are aware of might show more than 2. If you don't get what I"m saying, hopefully it will make sense when I send the code later. :) Mark