Try OpenEdge Now
skip to main content
Developing WebSpeed Applications
Controlling WebSpeed Transactions : Defining state

Defining state

Web transactions are, by nature, stateless. In other words, there is no sustained connection between a Web server and a client. Also, the Web server does not maintain any information about a client for future reference. Each transaction terminates after a response (usually an HTML page) is returned to the browser.
However, it is also possible to implement WebSpeed applications that are state-passing or state-persistent. State-passing applications store information about prior transactions on the client side. State-persistent applications maintain a connection between the client and the WebSpeed agent for some period of time.
* Web object states
* WebSpeed application states
* Advantages and drawbacks of state-persistence