About State

The GridServer technology allows Services to have a state—per-client or global—that is preserved by the container and is consistent across all physical Service instances, that is, all Engine-side instantiations of a client-side Service instance. The latter concept is important to understand: since many GridServer Engines can perform Service requests in parallel, the Service deployer must inform GridServer which methods are responsible for state and which are not. This way, GridServer can ensure that the object’s state is up-to-date prior to servicing the next request. In addition to the state, the container must know which methods to expose as Service operations and which methods to call for initialization and destruction of the Service implementations in memory.