66ec16006e
* Issue #5088 Review ContextHandler locking The locking was primarily as a memory guard for the availability status, which was already volatile. Have instead using an AtomicReference with a simple state machine layered on top of start/stop lifecycle. There was also protection for AttributesMap, which is no longer needed as AttributesMap is now concurrent. * Issue #5088 updates from review * Issue #5088 updates from review (better this time) |
||
|---|---|---|
| .. | ||
| src | ||
| pom.xml | ||