At 11:06 12.08.2002, Stefan Roehrich wrote: >On 2002-08-11 02:32:50, Yasuo Ohgaki wrote: > > Log: > > Changed my mind. > > Let users decided whether users want larger chunk size or not. > > @ Changed zlib.output_compression behavior. If larger chunk is preferred, > > enable output_buffering also. (Marcus, Yasuo) > >The NEWS entry got truncated, can you fix this? > >What's the benefit of the new behaviour? I think the old one was a >rather good default, because compression of small chunks doesn't make >sense and you could change the size via zlib.output_compression. > > Stefan
Yasuo, Zeev and me had a short discussion about internals and all the behaviour on the weekend. In short the old behavior was that we had zli.output_compression defaulting to 4K inputchunks (resulting normally in 1K output chunks) and a double buffer getting the input from zlib with a buffer size of 40K resulting in 40 output chunks. We will drop the double buffer again and my favorite would be changing zlibs default to 16K (resulting in 4K output chunks). But we must document this stuff.... If Zeev and Yasuo agree i will change the above later on today. Questions leeft: Maybe we should also change the default for output_buffering from 40K to 4K. Maybe we should change all default from 40K to 4K or use the value normally used for output_buffering (40K or 4K) as default size for other buffers. regards marcus -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
