Called when the connection has changed to {@link ConnectionState#RECONNECTED}
This is exposed so that users of the class can be notified of issues that might affect normal operation. The TreeCache is written such that listeners are not expected to do anything special on this event, except for those people who want to cause some application-specific logic to fire when this occurs. While the connection is down, the TreeCache will continue to have its state from before it lost the connection and after the connection is restored, the TreeCache will emit normal child events for all of the adds, deletes and updates that happened during the time that it was disconnected.
After reconnection, the cache will resynchronize its internal state with the server, then fire a {@link #INITIALIZED} event.
Called when the connection has changed to {@link ConnectionState#SUSPENDED}
This is exposed so that users of the class can be notified of issues that might affect normal operation. The TreeCache is written such that listeners are not expected to do anything special on this event, except for those people who want to cause some application-specific logic to fire when this occurs. While the connection is down, the TreeCache will continue to have its state from before it lost the connection and after the connection is restored, the TreeCache will emit normal child events for all of the adds, deletes and updates that happened during the time that it was disconnected.
Posted after the initial cache has been fully populated.
On startup, the cache synchronizes its internal state with the server, publishing a series of {@link #NODE_ADDED} events as new nodes are discovered. Once the cachehas been fully synchronized, this {@link #INITIALIZED} this event is published. All events published after this event represent actual server-side mutations.
On reconnection, the cache will resynchronize its internal state with the server, and fire this event again once its internal state is completely refreshed.
Note: because the initial population is inherently asynchronous, so it's possible to observe server-side changes (such as a {@link #NODE_UPDATED}) prior to this event being published.
A node was added.
A node was removed from the tree
A node's data was changed
Generated using TypeDoc
Called when the connection has changed to {@link ConnectionState#LOST}
This is exposed so that users of the class can be notified of issues that might affect normal operation. The TreeCache is written such that listeners are not expected to do anything special on this event, except for those people who want to cause some application-specific logic to fire when this occurs. While the connection is down, the TreeCache will continue to have its state from before it lost the connection and after the connection is restored, the TreeCache will emit normal child events for all of the adds, deletes and updates that happened during the time that it was disconnected.