[SLING-4684] Stress that handleTopologyEvent() should be lock-free and terminate quickly

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Discovery API 1.0.2
• Fix Version/s: Discovery API 1.0.4
• Component/s: Extensions
• Assignee: Stefan Egli
• Reporter: Stefan Egli
• Created: 30/Apr/15 10:22
• Updated: 30/Apr/15 10:26
• Resolved: 30/Apr/15 10:26

Description

The TopologyEventHandler.handleTopologyEvent() javadoc should be updated with:

• the fact that it should terminate quickly and not do any length operations (as this could potentially hold back any other handler and it was not intended to support long-running handle calls)
• the fact that the handleTopologyEvent() caller could potentially hold locks and handleTopologyEvent() itself should be (dead-)lock free

Issue Links

• is related to: SLING-4683 Ensure that topology change events are processed quickly