This is an automated email from the ASF dual-hosted git repository.

rombert pushed a commit to branch master
in repository 
https://gitbox.apache.org/repos/asf/sling-org-apache-sling-discovery-api.git

commit 709f9a771b8206cf02a9022cc1e8268552c7b6fd
Author: Stefan Egli <stefane...@apache.org>
AuthorDate: Thu Apr 30 10:25:07 2015 +0000

    SLING-4684 : Stress that handleTopologyEvent() should be lock-free and 
terminate quickly
    
    git-svn-id: https://svn.apache.org/repos/asf/sling/trunk@1676949 
13f79535-47bb-0310-9956-ffa450edef68
---
 src/main/java/org/apache/sling/discovery/TopologyEventListener.java | 4 ++++
 1 file changed, 4 insertions(+)

diff --git 
a/src/main/java/org/apache/sling/discovery/TopologyEventListener.java 
b/src/main/java/org/apache/sling/discovery/TopologyEventListener.java
index 8e199ce..71e1ff2 100644
--- a/src/main/java/org/apache/sling/discovery/TopologyEventListener.java
+++ b/src/main/java/org/apache/sling/discovery/TopologyEventListener.java
@@ -34,6 +34,10 @@ public interface TopologyEventListener {
         * Inform the service about an event in the topology - or in the 
discovery
         * of the topology.
         * <p>
+        * Implementors of this method must ensure that this method returns 
quickly
+        * and that no locks are being acquired that could cause deadlocks (ie 
the
+        * framework might call this method holding locks).
+        * <p>
         * The <code>TopologyEvent</code> contains details about what changed.
         * The supported event types are:
         * <ul>

-- 
To stop receiving notification emails like this one, please contact
"commits@sling.apache.org" <commits@sling.apache.org>.

Reply via email to