Support for EntityCache

yep, I'd like to see that happen asap. Any tackers?

OK, here is a very rudimentary attempt to make 'entity cache' something pluggable and delegates calls to it in all the moments entitycache seems to need them at the moment.

Pretty sure this works at the moment if entitycache's EntityCacheControllerHelper is passed as the 'entity cache' value in hook_entity_info_alter() as long as EntityCacheControllerHelper's methods are changed from protected to public.

Crosslinking: #1165930: Compatibility with Entity API.

patch looks good to me. I guess we should add some usage instructions to the README?

Is it support specifically for Entity cache that is desired, or persistent caching for EntityAPIController, with EntityCacheControllerHelper as a means to that end?

Definitely subscribing!
I'm coming from this issue: #1165930: Compatibility with Entity API

@quartsize: the approach I took was the more general one. So this patch works persistent caching into EntityAPIController delegating everything to the class found in the 'entity cache' property of the entity info.

Which allows the persistent cache handler to be swapped out if necessary.

Having said that, I made it work with EntityCache in mind, I haven't thought about what other persistent caching mechanisms may exist and may require so any thoughts you have about making it sufficiently flexible are welcome =)

Note, the complimentary issue on entitycache module has been committed (#1165930: Compatibility with Entity API)

So only README lines are should be done to make this happen. Seem this patch needs reroll but let's test it.

#2: entity-1111120-3-support-for-entitycache.patch queued for re-testing.

entity cache module defines the entity cache property as TRUE / FALSE - let's follow that and just use the class provided by the entity cache module.
Also I'm not keen on introducing a 'entity cache' property supporting arbitrary classes or without any interface or base class to extend. The latter could already be considered bad practice...

ok, I've implemented it that way and committed it. See attached patch.

I can't see this in the repository.. maybe you forgot to push? :)

exactly.. sry, pushed it now.