This repository has been archived by the owner on Jan 5, 2022. It is now read-only.
Repush to 2.1.1 with compatibility and bug fixes #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added running_count method to Mediator
Added fix for fatal error during worker cleanup that fixes issue shaneharter#41
Fix Memcache lib Refactore Lock plugins code to be more eficient
shaneharter
added a commit
that referenced
this pull request
May 4, 2014
Repush to 2.1.1 with compatibility and bug fixes
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The only backward incompatible change in this update is that Core_Lock_Lock::set() is now protected, not public, so custom lock plugins should be updated to conform this. Also it would be good (but not required) to remove checking logic from custom set() methods and limit their functionality to lock setting only.