Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue/102 #119

Merged
merged 6 commits into from
Jun 19, 2024
Merged

Issue/102 #119

merged 6 commits into from
Jun 19, 2024

Conversation

JJJ
Copy link
Collaborator

@JJJ JJJ commented Oct 26, 2020

See #102

This change ensures that anyone calling tcp_cache_set() directly in their own custom code has a more reliable idea of whether this method call has failed.
This commit strictly divides the TCP cache methods to stop storing a local copy of the remote cache when a persistent cache exists elsewhere.

It also adds expirations to the local cache, in the event that the PHP request is allowed to process and hang for longer than the servers have collectively to be checked.
Even for master. No matter the tries remaining.

If TCP responsiveness is being checked and the connection to master goes down, it will exist in the cache.
JJJ added 3 commits June 6, 2022 17:53
Renames some protected methods to better match their intended TCP usages.

Because WordPress loads WPDB before the object cache, the persistent TCP cache implementation needs to carefully start the object cache manually.

Fixes #126.
@JJJ JJJ merged commit 73919ee into master Jun 19, 2024
1 check passed
@JJJ JJJ deleted the issue/102 branch June 19, 2024 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant