[wp-hackers] any plan about bufferizing the whole WP output?..

[dave jaggy]

Just realized what you have meant by adding it via plugin. Wow. So
easy. Gotta try it.

On Sat, Dec 27, 2008 at 4:45 PM, Viper007Bond <viper at viper007bond.com> wrote:
> +1 to Ew.
>
> And it's super easy to add via a plugin anyway. Just hook in at "init" to
> start it and "shutdown" to output it.
>
> On Fri, Dec 26, 2008 at 11:39 PM, DD32 <wordpress at dd32.id.au> wrote:
>
>> Ew.
>>
>> Avoid buffering at all costs.
>>
>> It means that the PHP script needs to finish executing before any of the
>> page is sent to the user, and adds some overhead.
>>
>> However, Some systems automatically buffer to compress the output.
>>
>> Plugins can also call any output buffer functions themselves if they wish
>> to
>> use an output buffer..
>>
>> 2008/12/27 dave jaggy <jayarjo at gmail.com>
>>
>> > Is there a plan around to bufferize the whole wordpress output, before
>> > it actually gets echoed to a remote client? I think this gotta be
>> > great, if one could fully manage (add/remove/alter) output before it
>> > (headers) gets sent. Is there any API development plan in this
>> > direction?
>> > _______________________________________________
>> > wp-hackers mailing list
>> > wp-hackers at lists.automattic.com
>> > http://lists.automattic.com/mailman/listinfo/wp-hackers
>> >
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>
> --
> Viper007Bond | http://www.viper007bond.com/ | http://www.finalgear.com/
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>