vmamidi commented on pull request #7470: URL: https://github.com/apache/trafficserver/pull/7470#issuecomment-812008563
> Interesting. Didn't we've a Fuzzy revalidation feature in the ATS core that solves a similar problem (at least for stale objects)? It looks like it's been removed (sorry, I don't have the context as to why), but wonder we should consider reviving that. It feels that it's an arguably better approach as it ensures the object always remains fresh in the Cache and avoids having to fire off 2 parallel requests to the Origin or even block the client request eventually? Fuzz had its problems. ATS cache update is not atomic, which makes it harder to implement fuzz properly. This plugin's eventual goal is to eliminate the penalty of origin/client speed while serving a client. This plugin only takes care of eliminating the slow client from the equation. Subsequently, I would like to make cache updates atomic and eventually get to implement fuzzy logic. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
