[wp-hackers] should (can?) wp-cache be adopted into the core?

[Viper007Bond]

Couldn't agree more. I'd love to see a output caching system built in (or
even better, as a bundled plugin to make it modular). While WordPress can
run great under most circumstances, some blogs are just too dang popular to
run without a super computer. Having something that is essentially core, but
easily loadable / unloadable (a plugin) would solve this problem and make
WordPress even more feasible / desirable for large bloggers.

Case in point: I have a WP powered site that gets around a million hits a
month. While I know I could run it without WP-Cache, I'd rather put the CPU
to better use (like handling the site's forums which get around another
million or two hits a month). Not having to hack WP-Cache to work and
knowing for sure it'd support future versions would be a godsend.

On 4/17/07, Matt Mullenweg <m at mullenweg.com> wrote:
>
> David Chait wrote:
> > Opinions?  Matt?  (since I think staticize was your baby originally,
> no?)
>
> Having a built-in output cache could be very powerful for the growing
> number of WordPress users who are climbing to the top of the blogosphere.
>
> There are a lot of issues to work out, as have been mentioned on this
> thread, so this is a good example of a project that needs a champion to
> take ownership of the issue and coordinate what needs to happen to get
> the plugin or functionality into a release like 2.3 or 2.4.
>
> --
> Matt Mullenweg
>   http://photomatt.net | http://wordpress.org
> http://automattic.com | http://akismet.com
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Viper007Bond | http://www.viper007bond.com/