THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
| ID | IEP-50 | ||||||||
| Author | |||||||||
| Sponsor | |||||||||
| Created |
| ||||||||
| Status |
|
| Table of Contents |
|---|
Motivation
...
- Cache update listener: while query is active, client receives events. Server → Client notification mechanism already exists for that (see IEP-42 Thin client: compute supportClient Compute).
- (Optional) Remote filter
...
Name | Code |
|---|---|
| OP_QUERY_CONTINUOUS | 2006 |
OP_QUERY_CONTINUOUS_EVENT_NOTIFICATION | 2007 |
OP_QUERY_CONTINUOUS starts the query.
Existing OP_RESOURCE_CLOSE should be used to stop stops the continuous query using the id provided in the OP_QUERY_CONTINUOUS response message.
...
| Response | |
|---|---|
| long | continuousQueryId - used to retrieve initial query data and stop the query with OP_RESOURCE_CLOSE |
Resulting continuousQueryId should be used to stop the query with OP_RESOURCE_CLOSE and (when applicable) retrieve initial query data with OP_QUERY_SCAN_CURSOR_GET_PAGE or OP_QUERY_SQL_CURSOR_GET_PAGE, respectively.
Note: AbstractContinuousQuery.autoUnsubscribe should be always true for thin client continuous queries.
As a result of OP_QUERY_CONTINUOUS and until OP_RESOURCE_CLOSE is called, client should expect OP_QUERY_CONTINUOUS_EVENT_NOTIFICATION messages from the server:
...
Tickets
| Jira | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Content Tools
Apps