You are viewing a plain text version of this content. The canonical link for it is here.
- [1/2] curator git commit: CURATOR-294: Make ChildData immutable; PathChildrenCache replaces instead of mutates. - posted by dr...@apache.org on 2016/02/01 20:15:11 UTC, 0 replies.
- [2/2] curator git commit: CURATOR-294: Optimize TreeCache, fix possible concurrency issue - posted by dr...@apache.org on 2016/02/01 20:15:12 UTC, 0 replies.
- curator git commit: TreeCache should inform listeners when its fully reconnected. - posted by dr...@apache.org on 2016/02/01 20:19:54 UTC, 0 replies.
- curator git commit: Merge branch 'master' into CURATOR-3.0 - posted by dr...@apache.org on 2016/02/01 20:36:55 UTC, 0 replies.
- [1/3] curator git commit: CURATOR-294: Make ChildData immutable; PathChildrenCache replaces instead of mutates. - posted by dr...@apache.org on 2016/02/01 21:16:03 UTC, 0 replies.
- [2/3] curator git commit: CURATOR-294: Optimize TreeCache, fix possible concurrency issue - posted by dr...@apache.org on 2016/02/01 21:16:04 UTC, 0 replies.
- [3/3] curator git commit: Merge branch 'master' into CURATOR-3.0 - posted by dr...@apache.org on 2016/02/01 21:16:05 UTC, 4 replies.
- curator git commit: Check that response stat is not null - posted by ra...@apache.org on 2016/02/02 15:33:07 UTC, 0 replies.
- curator git commit: Only create parent nodes in foreground if buildInitial is true - posted by ra...@apache.org on 2016/02/02 16:39:32 UTC, 1 replies.
- curator git commit: Because start() creates the node async, if close is called immediately, it might occur before the node creation. Handle this edge case by having the background response delete (async) the node if the instance has been closed - posted by ra...@apache.org on 2016/02/02 19:26:39 UTC, 0 replies.
- [1/3] curator git commit: TreeCache should inform listeners when its fully reconnected. - posted by ra...@apache.org on 2016/02/02 20:42:53 UTC, 0 replies.
- [2/3] curator git commit: Only create parent nodes in foreground if buildInitial is true - posted by ra...@apache.org on 2016/02/02 20:42:54 UTC, 0 replies.
- [1/2] curator git commit: Because start() creates the node async, if close is called immediately, it might occur before the node creation. Handle this edge case by having the background response delete (async) the node if the instance has been closed - posted by ra...@apache.org on 2016/02/02 22:39:03 UTC, 0 replies.
- [2/2] curator git commit: Merge branch 'CURATOR-297' - posted by ra...@apache.org on 2016/02/02 22:39:04 UTC, 0 replies.
- [1/3] curator git commit: Because start() creates the node async, if close is called immediately, it might occur before the node creation. Handle this edge case by having the background response delete (async) the node if the instance has been closed - posted by ra...@apache.org on 2016/02/02 22:48:46 UTC, 0 replies.
- [2/3] curator git commit: Merge branch 'CURATOR-297' - posted by ra...@apache.org on 2016/02/02 22:48:47 UTC, 0 replies.
- svn commit: r12186 - in /dev/curator: 2.3.0/ 2.3.1/ 2.4.0/ 2.4.1/ 2.4.2/ 2.5.0/ 2.6.0/ 2.7.0/ 2.7.1/ 2.8.0/ - posted by ra...@apache.org on 2016/02/02 22:53:36 UTC, 0 replies.
- svn commit: r12187 - in /release/curator: 2.3.0/ 2.4.0/ 2.4.1/ 2.4.2/ 2.5.0/ 2.6.0/ 2.7.0/ 2.7.1/ 2.8.0/ - posted by ra...@apache.org on 2016/02/02 22:55:15 UTC, 0 replies.
- svn commit: r12188 - /release/curator/2.9.0/ - posted by ra...@apache.org on 2016/02/02 22:58:35 UTC, 0 replies.
- svn commit: r12189 - /dev/curator/2.9.0/ - posted by ra...@apache.org on 2016/02/02 22:58:42 UTC, 0 replies.
- [1/2] curator git commit: Major re-work of Watcher wrappers. It really isn't necessary to keep a map of watchers. It was originally done so that watcher identity was maintained, but this can be achieved much easier using special-purpose hashCode() and eq - posted by ra...@apache.org on 2016/02/05 02:49:03 UTC, 0 replies.
- [2/2] curator git commit: The path should be part of NamespaceWatcher's identity. Also, I can simplify WatcherRemovalManager - posted by ra...@apache.org on 2016/02/05 02:49:04 UTC, 0 replies.
- curator git commit: No need to delete watcher. WatcherRemoveCuratorFramework does it automatically - posted by ra...@apache.org on 2016/02/05 18:21:29 UTC, 0 replies.
- [curator] Git Push Summary - posted by ra...@apache.org on 2016/02/05 22:09:03 UTC, 4 replies.
- curator git commit: CURATOR-302: fix TestTreeCache.testKilledSession() - posted by dr...@apache.org on 2016/02/08 18:24:38 UTC, 0 replies.
- [1/3] curator git commit: CURATOR-302: fix TestTreeCache.testKilledSession() - posted by ra...@apache.org on 2016/02/08 19:16:02 UTC, 0 replies.
- [2/3] curator git commit: Merge branch 'CURATOR-3.0' into CURATOR-299 - posted by ra...@apache.org on 2016/02/08 19:16:03 UTC, 0 replies.
- [3/3] curator git commit: compare of CuratorWatcher is needed too - posted by ra...@apache.org on 2016/02/08 19:16:04 UTC, 0 replies.
- curator git commit: more complete comment for clearWatcherReferences - posted by ra...@apache.org on 2016/02/08 19:17:54 UTC, 0 replies.
- [1/6] curator git commit: Major re-work of Watcher wrappers. It really isn't necessary to keep a map of watchers. It was originally done so that watcher identity was maintained, but this can be achieved much easier using special-purpose hashCode() and eq - posted by ra...@apache.org on 2016/02/08 19:18:27 UTC, 0 replies.
- [2/6] curator git commit: The path should be part of NamespaceWatcher's identity. Also, I can simplify WatcherRemovalManager - posted by ra...@apache.org on 2016/02/08 19:18:28 UTC, 0 replies.
- [3/6] curator git commit: No need to delete watcher. WatcherRemoveCuratorFramework does it automatically - posted by ra...@apache.org on 2016/02/08 19:18:29 UTC, 0 replies.
- [4/6] curator git commit: Merge branch 'CURATOR-3.0' into CURATOR-299 - posted by ra...@apache.org on 2016/02/08 19:18:30 UTC, 0 replies.
- [5/6] curator git commit: compare of CuratorWatcher is needed too - posted by ra...@apache.org on 2016/02/08 19:18:31 UTC, 0 replies.
- [6/6] curator git commit: more complete comment for clearWatcherReferences - posted by ra...@apache.org on 2016/02/08 19:18:32 UTC, 0 replies.
- [1/2] curator git commit: Add note to explain why service providers should be cached/reused - posted by ra...@apache.org on 2016/02/08 19:21:34 UTC, 0 replies.
- [2/2] curator git commit: Merge branch 'CURATOR-286' of github.com:joelittlejohn/curator into CURATOR-286 - posted by ra...@apache.org on 2016/02/08 19:21:35 UTC, 0 replies.
- [1/3] curator git commit: Add note to explain why service providers should be cached/reused - posted by ra...@apache.org on 2016/02/08 19:21:54 UTC, 0 replies.
- [2/3] curator git commit: Merge branch 'CURATOR-286' of github.com:joelittlejohn/curator into CURATOR-286 - posted by ra...@apache.org on 2016/02/08 19:21:55 UTC, 0 replies.
- curator git commit: TreeCache debug logging - posted by dr...@apache.org on 2016/02/08 19:37:36 UTC, 0 replies.
- svn commit: r12276 - in /dev/curator: 2.10.0/ 3.1.0/ - posted by ra...@apache.org on 2016/02/08 19:56:10 UTC, 0 replies.
- curator git commit: Fix TestTreeCache pollution; more tearDown() checks. - posted by dr...@apache.org on 2016/02/10 00:11:07 UTC, 0 replies.
- [1/3] curator git commit: TreeCache debug logging - posted by dr...@apache.org on 2016/02/10 00:13:54 UTC, 0 replies.
- [2/3] curator git commit: Fix TestTreeCache pollution; more tearDown() checks. - posted by dr...@apache.org on 2016/02/10 00:13:55 UTC, 0 replies.
- svn commit: r12329 - in /dev/curator: 2.10.0/ 3.1.0/ - posted by ra...@apache.org on 2016/02/10 14:50:22 UTC, 0 replies.
- [1/4] curator git commit: [maven-release-plugin] prepare release apache-curator-3.1.0 - posted by ra...@apache.org on 2016/02/10 15:29:45 UTC, 0 replies.
- [2/4] curator git commit: [maven-release-plugin] prepare for next development iteration - posted by ra...@apache.org on 2016/02/10 15:29:46 UTC, 0 replies.
- [3/4] curator git commit: Merge branch 'CURATOR-3.0' of https://git-wip-us.apache.org/repos/asf/curator into CURATOR-3.0 - posted by ra...@apache.org on 2016/02/10 15:29:47 UTC, 0 replies.
- [4/4] curator git commit: Added some additional tests to validate NamespaceWatcher identity - posted by ra...@apache.org on 2016/02/10 15:29:48 UTC, 0 replies.
- curator git commit: Don't allow NamespaceWatcher to compare equal to a raw Watcher or CuratorWatcher. It can't be done reciprocally in a raw Watcher and is actually unnecessary. NOTE: a Curator Tech Note should be written to warn that Watchers are wrappe - posted by ra...@apache.org on 2016/02/10 18:22:36 UTC, 0 replies.
- [1/2] curator git commit: NamespaceWatcher should only equals other NamespaceWatcher - posted by ra...@apache.org on 2016/02/10 19:04:19 UTC, 0 replies.
- [2/2] curator git commit: Merge branch 'identity' of github.com:dragonsinth/curator into identity - posted by ra...@apache.org on 2016/02/10 19:04:20 UTC, 0 replies.
- svn commit: r12333 - in /dev/curator: 2.10.0/ 3.1.0/ - posted by ra...@apache.org on 2016/02/10 21:24:26 UTC, 0 replies.
- Scan from KM1650 - posted by sc...@curator.apache.org on 2016/02/11 11:53:42 UTC, 0 replies.
- svn commit: r12388 - in /release/curator: 2.10.0/ 3.1.0/ - posted by ra...@apache.org on 2016/02/15 01:45:10 UTC, 0 replies.
- svn commit: r12389 - in /release/curator: 2.9.1/ 3.0.0/ - posted by ra...@apache.org on 2016/02/15 01:47:21 UTC, 0 replies.
- svn commit: r12390 - in /dev/curator: 2.9.1/ 3.0.0/ - posted by ra...@apache.org on 2016/02/15 01:47:33 UTC, 0 replies.
- svn commit: r1730440 - in /curator/site/trunk: ./ apidocs/ apidocs/cache/ apidocs/cache/class-use/ apidocs/discovery/ apidocs/discovery/class-use/ apidocs/framework/ apidocs/framework/class-use/ apidocs/leader/ apidocs/leader/class-use/ apidocs/locking... - posted by ra...@apache.org on 2016/02/15 02:48:52 UTC, 0 replies.
- Scanned image - posted by admin <an...@curator.apache.org> on 2016/02/29 20:02:47 UTC, 0 replies.