A mechanism by which the Navigator client can store small items of information on the client machine; one of the methods that LiveWire uses to maintain properties of the client object.
An attempt to perform all the database actions in a transaction; the commit may succeed or fail, depending on the actions and the state of the database.
A data structure returned by a database query, consisting of an answer set and a pointer to a row in the answer set; the LiveWire cursor object has corresponding properties and methods.
The page specified in Application Manager that a client will access, if the user requests an application URL, but no specific page in the application. Compare to initial page.
To transfer a managed site to a location where others can access it. The location can be on the local server's file system or a remote server connected to the Internet.
A server accessible to end-users on which a LiveWire application is installed, also called a production server. Should be different from the development server.
A server, typically inside a firewall, on which you develop and test LiveWire applications, not accessible to end-users. Should be different from the deployment server.
One of LiveWire's techniques for maintaining the client object, in which the server generates a unique name for a client, and uses it to refer to a data structure containing client property values. The name is then stored on the client using the Netscape cookie protocol.
One of LiveWire's techniques for maintaining the client object, in which the server uses the client's IP address to refer to a data structure containing client property values.
One of LiveWire's techniques for maintaining the client object, in which the server generates a unique name for a client, and uses it to refer to a data structure containing client property values. The name is then appended to the client's requested URLs.