The most common use case for this is when the validation is done on a remote server.
They have several advantages over similar hooks in other lower-level frameworks: , however, you don’t necessarily expect the server to give you the full resource back.
Invalidating postdata getting back to dating after a break up
The property can specify multiple comma-delimited repositories, and each repository can specify multiple semi-colon-delimited item descriptors.
It is possible to invalidate individual fields from the controller without the use of the Validator class.
Ultimately the result of a POST request should be a cache invalidation, not an addition or the return of a cached result.
I was in a situation where I was providing a HTTP service where if you make a request the response won’t change for at least the next X minutes, no matter who requests it.
Because when it comes to knowing the state of the data and when to invalidate, the server knows best, I believe the caching is the responsability of the server and should be taken care of by the server.
But sometimes you do not have control over the caching headers, for example when using a third party API.
I couldn’t adjust the way requests were sent to this service, which were POST SOAP requests, so I had to find a way to cache the results without changing the input.
So I thought that since Varnish is pretty much caching software, it would solve my problems (spoiler alert… However I had a few problems to work out before I found that out.
In those cases you do not want your application to make multiple of the same requests over and over again.
Configuring the caching clientside might come in handy in those circumstances.
Two general constraints apply to usage of selective cache invalidation: A production site publishing agent can be configured to exclude specific repositories and item descriptors from selective cache invalidation—in other words, require that item caches be fully invalidated on each deployment.