anchor.diff:  - **Interest criteria based on data values**. CQ queries are run against the region's entry values. 
   Compare this to register interest by reviewing [Registering Interest for Entries](../client-cache/registering-interest-for-entries.html).
   
  --   **Active query execution**. Once initialized, the queries only operate on new events instead of on the entire region data set. 
  +-   **Active query execution**. Once initialized, the queries operate only on new events, rather than on the entire region data set. 
   Events that change the query result are sent to the client immediately.
   
   ## <a id="typical_cq_lifecycle"></a>Typical CQ Lifecycle
  
positive.code: 2.  The client runs the CQ with an API call to one of the `CqQuery execute*` methods. This puts the query into a `RUNNING` state on the client and on the server.
  3.  The CQ is closed by a client call to `CqQuery.close`. This de-allocates all resources in use for the CQ on the client and server. At this point, the cycle could begin again with the creation of a new `CqQuery` instance.
  
  
negative.code: 
  Continuous querying in the native client has the following features:
  
  -   **Standard <%=vars.product_name%> native client query syntax and semantics**. CQ queries are expressed in the same language used for other native client queries. See [Remote Queries](../remote-querying/remote-queries.html).
  
  - **Standard <%=vars.product_name%> events-based management of CQ events**. The event handling used
  to process CQ events is based on the standard <%=vars.product_name%> event handling framework. 
  