Re: WML/WAP and PHP

At 9:08 AM -0800 1/16/01, Chris Adams wrote:

On 16 Jan 2001 05:05:18 -0800, Rick Hodger <rick@domainsbuy.com> wrote:

[0] neat hack - use ob_content_length() to tell when you've output almost as much data as the phone can handle (find this by doing a browser detect) so you can stop looping over a recordset and emit the Next/Prev page headers instead).

This is indeed very neat (and shows that PHP is made with the web in mind, and not just another language that can add interaction to the web). Please bear in mind that output buffering seems to be buggy on some platforms (http://bugs.php.net/?id=8709) Since WAP implies *many* short connections this would turn the server to stop responding quickly. I haven't have time to verify more, but it seems the size of the apache deamons in memory are smaller too (they used over 80MB per process before), when I stopped using output buffering the size of the process dropped to 12-13MB (still big, but that's about the size they get on a RISC system) -- Thierry Coopman - thierry@keytrade.com My opinions are personal, and have really nothing or nothing to do with Keytrade! You know that you are drinking too much coffee if: ... Instant coffee takes too long.