# Glossary

active application

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