anchor.diff:  <tr>
   <td><code class="ph codeph">AsyncEventListener</code></td>
   <td><code class="ph codeph">AsyncEvent</code></td>
  -<td><p>Tracks changes in a region for write-behind processing. Extends th <code class="ph codeph">CacheCallback</code> interface. You install a write-back cache listener to an <code class="ph codeph">AsyncEventQueue</code> instance. You can then add the <code class="ph codeph">AsyncEventQueue</code> instance to one or more regions for write-behind processing. See [Implementing an AsyncEventListener for Write-Behind Cache Event Handling](implementing_write_behind_event_handler.html#implementing_write_behind_cache_event_handling).</p></td>
  +<td><p>Tracks changes in a region for write-behind processing. Extends the <code class="ph codeph">CacheCallback</code> interface. You install a write-back cache listener to an <code class="ph codeph">AsyncEventQueue</code> instance. You can then add the <code class="ph codeph">AsyncEventQueue</code> instance to one or more regions for write-behind processing. See <a href="implementing_write_behind_event_handler.html#implementing_write_behind_cache_event_handling">Implementing an AsyncEventListener for Write-Behind Cache Event Handling</a>.</p></td>
   </tr>
   <tr>
   <td><code class="ph codeph">CacheCallback</code></td>
  
positive.code: <td>Receives events for <em>pending</em> changes to the region and its data entries in this member or one of its peers. Has the ability to abort the operations in question. Extends <code class="ph codeph">CacheCallback</code> interface. Installed in region. Receives events from anywhere in the distributed region, so you can install one in one member for the entire distributed region. Receives events only in primary data store in partitioned regions, so install one in every data store.</td>
  </tr>
  <tr>
  <td><code class="ph codeph">ClientMembershipListener</code>
  <p>(org.apache.geode.management .membership.ClientMembershipListener)</p></td>
  <td><code class="ph codeph">ClientMembershipEvent</code></td>
  <td>One of the interfaces that replaces the deprecated Admin APIs. You can use the ClientMembershipListener to receive membership events only about clients. This listener's callback methods are invoked when this process detects connection changes to clients. Callback methods include <code class="ph codeph">memberCrashed</code>, <code class="ph codeph">memberJoined</code>, <code class="ph codeph">memberLeft</code> (graceful exit).</td>
  </tr>
  
negative.code: </tr>
  <tr>
  <td><code class="ph codeph">UniversalMembershipListenerAdapter</code>
  <td><code class="ph codeph">MembershipEvent</code> and <code class="ph codeph">ClientMembershipEvent</code></td>
  <td>One of the interfaces that replaces the deprecated Admin APIs. Provides a wrapper for MembershipListener and ClientMembershipListener callbacks for both clients and peers.</td>
  </tr>
  