Actually, if you use the functions, you will have no problems, a few functions were removed, but all of the functions that plugin authors and core uses are still there and will remain. The only functionality that was removed was the enable cache and disable cache constants, so you can only disable the cache by using the new constant and replacing the current cache.

By using the caching functions you are doing your users a favor, so keep up that good work!

@Jacob Santos: I’ll definitely continue to code for them, but my concern is on the sysadmin side. The disk-based system is easy (if obviously not as efficient as a persistent memory-backed cache). I just need to learn more about that part.

I found some problem in using Object Cache in WordPress 2.5.

I have use the function wp_cache_set to cache the object, then I use the function wp_cache_get to get the object, but it return false.

the cache function in my plugin works in WordPress 2.3, but it doesn’t work on WordPress 2.5

can you help me to have a look my plugin?
my plugin is http://wordpress.org/extend/plugins/top-first-commentors/

thanks in advance

I will say, that it appears that you are setting the top commentors after you call the get cache function. Following the logic, your plugin would preform best with disk caching where it would just pull from that.

I would keep it like that or use another caching plugin. Currently, it appears that you are caching it to memory after you try to get it, which doesn’t help on the next page load when it must still preform the SQL query.

I just finished posting about the changes to the WP object caching system, including a history of WordPress’s caching abilities and memory-based extensions to the WP object cache that are WP 2.5 compatible… Hopefully it’ll provide some further insight into the matter: http://neosmart.net/blog/2008/wordpress-25-and-the-object-cache/