Pierre, At first we thought revServer hiccup was a "wake-up call"--which is also not acceptable, but further investigation lead us to believe that is not the case. Some sort of pooling of requests within the 30 seconds seems a more logical explanation. However, this is academic to us. We've always factored our revServer code for the easiest possible migration to PHP, which we are now doing.
Best, Jerry Daniels Follow the Rodeo discussion: http://rodeoapps.com/discuss-among-yourselves-0 On Aug 2, 2010, at 10:54 AM, Pierre Sahores wrote: > Exact : i can see this happen with the early requests to woooooooords.com : > The first request can, time to time, take around 20 secs. to get it's > response back to the end-user's browser. After this first request, the next > ones are always back to the user in less than some ticks. Could be a problem > related to the RAM virtualisation of the RHEL5 host it self, httpd.conf, > etc... and, please RunRev, we all need to get this fixed. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
