add new cache mechanism for more fine grained cache control

[AaronJan]

[rjsworking]

Hi

Don't know the planned features for the new cache mechanism but it would be nice to selectivly enable cache with different cache drivers and TTL.

Let's say you have yoursite.tld/about cached. As the "about" data is not changed frequently, this could be cached with the file cache driver and have a 1 month TTL.
But for article comments, you may want to cache on memcached or redis with a 5 minute TTL.

Events attached to the model would be nice too. If you change data and the data is cached then cache should be cleared and created again taking in account the driver and ttl.

Keep up the good work.

Cheers

[AaronJan]

Yes, this is the place to discuss about the cache mechanism 😄

Separate cache drivers is a interesting idea, I think the new cache thing should be powerful like this (yet simple to use).

I'm not sure about the model event stuff, I think it will make things complicated. If we just use the repository to deal with data, then not need to attaching event handler to model.

Thank you for you feedback @rsdev000 !

[rjsworking]

Hi. I've left a comment in the laracasts thread.

You're right. The model event stuff is not so important and can be added outside the package if needed.

Separate cache drivers is the most important feature. Not all users have redis available even on company dedicated servers. Sometimes only memcache is available. An in shared hosting servers, there's no redis nor memcache and the solution is to store cache in files.

[Edited]
I have another suggestion. If one uses the CacheStatically trait, then cache should be enabled by default. Otherwise there's no need to use the trait. If for some reason you don't want to cache the results from some method then you can do $repo->disableCache().

Cheers

[AaronJan]

I do struggled about the default setting of the CacheStatically, you are not the first one to ask this. I think I may change this in 2.4.

If you have other thoughts, feel free to comment here.

👍 Cheers.

[AaronJan]

Got a solution, working on it.