|active application||A LiveWire application that has been started, and can therefore be run, or accessed, by clients.
||A result returned by a database query, consisting of rows and columns that match the constraints specified by the SELECT statement
||The name of a LiveWire application, as specified in Application Manger. Clients use the application URL to access an application
|| Binary Large Object, the format of binary data stored in a relational database
|| Platform-independent object code, intermediate between source code and platform-specific machine code.
|| Common Gateway Interface, used to create server-based Web applications with languages such as Perl or C.
|| 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.
||client URL encoding
|| One of the methods that LiveWire uses to maintain properties of the client object, appending name/value pairs to the URL string.
||commit a transaction
|| 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 row in a table referenced by a database cursor.
|| In a database application, the active transaction under which all database actions are performed.
|| 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.
|| Data Definition Language, database statements to create, alter, or delete database objects such as tables, keys, stored procedures, and so on.
|| 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.
|| Dynamic Link Library, the format for shared libraries on Windows operating systems.
|| Functions defined in native libraries (DLLs or SOs), that can be used in LiveWire applications
|| Hypertext Markup Language, the language used to define pages for the World-Wide Web.
|| Hypertext Transfer Protocol, the communication protocol used to transfer information between Web servers and clients.
|| The page specified in Application Manager that a client will access if it has not yet accessed the application. Compare to default page.
|| A set of four numbers between 0 and 255, separated by periods that specifies a location for the TCP/IP protocol.
|| The degree to which multiple simultaneous transactions in the same database affect each other.
|| Multipart Internet Mail Extension, a standard specifying the format of data transferred over the internet.
|| A database transaction occurring within another transaction.
||Netscape cookie protocol
|| Netscape's format for specifying the parameters of a cookie in the HTTP header.
|| LiveWire's four objects: request, client, project, and server, that provide a foundation for application development.
|| Open Database Connectivity, Microsoft's interface for relational database programming.
|| SQL statements which an application literally "passes through" to the database server.
|| Relational Database Management System
||roll back a transaction
|| To cancel all the database actions within one transaction.
|| 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.
||server IP address
|| 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.
||server URL encoding
|| 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.
|| Shared Object, the format for shared libraries on Unix operating systems.
|| Structured Query Language, a standard language for defining, controlling, and querying relational databases.
|| An application which has been stopped with Application Manager, and is not accessible to clients.
|| Transport Control Protocol / Internet Protocol, the communications protocol used by the internet.
|| A group of database actions that are performed together; all the actions will succeed, or all will fail.
|| A database cursor in which you can update tables based on the contents of the answer set.
|| Universal Resource Locator, the addressing scheme used by the World-Wide Web.
|| The compiled form of a LiveWire application; contains bytecodes. Must be installed to run by a Netscape server.
|| What You See Is What You Get