[wp-hackers] GSoC Proposal: Integrate WP-cache / WP Super Cache
into WordPress
DD32
wordpress at dd32.id.au
Sat Mar 1 03:49:50 GMT 2008
Sorry for the confusion - I'll rephrase, but wont be saying exactly the same things.. simply due to my confusion :)
What i meant, Was that While a HTML cacher would be nice in the core, it is a bit of a hard compromise in terms of configuration.
The HTML cachers currently hook in before the database has been connected to, and as such, only the options set in the config file are available. So it'd either be allways enabled, or allways disabled at that point, There wouldnt be much user configuration available via the admin interface for the caching as a result. (writing to the filesystem is allways problematic for saving options).
The Object Cache was removed due to the problems with maintaining it, problems such as filesystem access(permissions, and/or speed); A HTML cache would have the exact same problems.
While the HTML caching could take place after the database has been connected to, to allow for generalistic options to be set, it would remove a main benefit of having the caching installed in the first place - That is, That quite often the problem is that MySQL goes down under heavy load.
On Sat, 01 Mar 2008 14:36:52 +1100, Ronald Heft <ron at cavemonkey50.com> wrote:
> DD32,
> I'm not exactly sure what you're referring to with plugins. Are you saying
> that including an HTML caching solution directly into WordPress is a good
> idea as plugins are no longer guessing if WP-cache is installed, or are you
> saying something else?
>
> On Fri, Feb 29, 2008 at 1:37 AM, DD32 <wordpress at dd32.id.au> wrote:
>
>> Just a quick note:
>>
>> Keep in mind that the Object Cache has been removed from WordPress 2.5 (By
>> default; Users can still add-in memcached/mysql memory tables/the original
>> object cache via the override file wp-content/object-cache.php)
>>
>> The main reason for removing it was that it was not enabled by default,
>> and that there were more issues with it than benifits(IMO).
>>
>> A HTML Cacher would be a nice inclusion in core, But its hard to enable as
>> pure included plugin material, Due to the fact that its either enabled or
>> disabled according to the file being present in wp-content/ or not.
>>
>> I think WordPress would benefit more from only loading the required files
>> in the long run, As thats something that Plugins cannot help with.
>>
>> On Fri, 29 Feb 2008 17:29:42 +1100, Matt <speedboxer at gmail.com> wrote:
>>
>> > On Thu, Feb 28, 2008 at 10:17 PM, Ronald Heft <ron at cavemonkey50.com>
>> wrote:
>> >> Regarding things like APC and memcache, correct me if I'm wrong, but I
>> do
>> >> not think the majority of web hosts would be able to support those
>> >> solutions. Very few people would benefit.
>> >
>> > I don't think APC and memcache work as well in shared environments...
>> >
>> > It'd be interesting to see what kind of plugins would be made off of
>> > such a system. A plugin that changes the theme when the site's under
>> > stress would defiantly be interesting.
>> >
>> >
>>
>>
>>
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>
>
>
More information about the wp-hackers
mailing list