This section describes session state and persistent state information, which enables users to use the same information in more than one invocation.
An adapter's execute() function can be called many times. Many adapters need to carry over information from one invocation to the next. For example, if you write an output adapter that writes to a file, after you open that output file you will want to store a file pointer to that file so you can write to the file each time without the overhead of reopening the file. We refer to this carried over information as session state, and the Sybase CEP C/C++ SDK provides functions that allow you to store and retrieve session state. Session state information is not carried over if the server crashes or is restarted.
Persistent State information is much like Session State information, except that if Persistence was enabled for the query module that is using this adapter instance, then Persistent State information will persist across system restarts and crashes.