@treeflips We have chosen not to add object caching to Comet Cache because object caching is very prone to causing problems with other WordPress plugins, i.e., other plugins must be written with object caching in mind to work properly when object caching is enabled and many WordPress plugins are not, which can lead to all sorts of strange issues. That’s why when it comes to WordPress and object caching, it’s best to implement object caching as part of a bigger overall deployment strategy where each plugin you’re running has been specifically optimized (or at least thoroughly reviewed) for object caching.
Another reason we’ve chosen not to focus on object caching at this time is that object caching in WordPress would save you database queries, however when you’re running a page caching plugin like Comet Cache, there are no database queries happening when Comet Cache serves a cached page (that’s what makes it fast). Also, the WordPress Core is already very optimized and includes a lot of built-in object caching, further reducing the need for adding this to a plugin.
Regarding Memcached / Redis: The next version of Comet Cache Pro (coming out very soon) will include support for Memcached / Redis. ??