In addition, other Netscape books discuss certain aspects of JavaScript particularly relevant to their topic area. These books are mentioned where relevant throughout this book. The Netscape web site contains much information that can be useful when you're creating JavaScript applications. Some URLs of particular interest include:
http://home.netscape.com/one_stop/intranet_apps/index.html
http://help.netscape.com/products/tools/livewire
http://developer.netscape.com/one/javascript/ssjs/index.html
Lock class allows safe sharing of information with multiple incoming requests. See "Sharing Objects Safely with Locking".
SendMail class lets you generate email from JavaScript. See "Mail Service".
project, server, and request objects. In particular, you can now use project and server objects to store references to other objects. See "The project Object", "The server Object", and "The request Object".
Direct access to HTTP request and response headers. See "Request and Response Manipulation".
livewire.conf file is upgraded and renamed jsa.conf. The new jsa.conf file points to the new Application Manager and the new sample applications. It also contains entries for all other applications you had in the old livewire.conf file. For details of the jsa.conf file, see "Application Manager Details".
LiveWire/docs directory, you must move (or copy) them to a new directory. In addition, you must manually recompile user-defined applications before you can use them with a 3.x web server, as described in "Backward Compatibility with Earlier Releases". Be aware that an application can't be used with Enterprise Server 2.0 after recompiling. If you want to use an application with both servers, you should copy the application instead of moving it.
world, hangman, cipher, dbadmin, and viewer sample applications. In addition, the sample application lwccall has been updated and renamed jsaccall. The sample application video has been updated and renamed oldvideo; a new version of this application, using new LiveWire Database Service features, is named videoapp. Finally, there are several new sample applications, bank, bugbase, flexi, and sendmail, that demonstrate other new server-side JavaScript features. For information on the sample applications, see Chapter 2, "Introduction to the Sample Applications."
samples directory and you want to transfer your changes to the new server, you must move (or copy) them and recompile them, as you do your own applications.
lwcomp. It is now called jsac and has additional options. For information on using the compiler, see "Compiling an Application". Once you recompile your applications, they will not work under LiveWire 1.x.
obj = new Object();
obj.prop = 42;
write(obj[0] == 42); //Illegal! Cannot refer to obj.prop as obj[0]
NULL. In this release, it returns undefined. Consider this code: <server>
var myVar;
write("The value of myVar is: " + myVar);
<server>
The value of myVar is: NULLNow it produces this output:
The value of myVar is: undefined
client and request objects for an application's initial page. The properties of this client object were not available on other pages. In this release, the runtime engine creates neither a client object nor a request object for an application's initial page. You can use the following statements to create these objects:client = new Object();
request = new Object();
project.lock or server.lock, and if another thread then calls the same method, that method will wait until the first thread calls project.unlock or server.unlock or until a specified timeout period has elapsed. If, however, the second thread does not call project.lock or server.lock, it can make changes to those objects. For more information on locking, see "Sharing Objects Safely with Locking".DbPool objects and close all cursors opened either with database or Connection objects. For information on managing connections, see Chapter 8, "Connecting to a Database." For information on cursors, see "Manipulating Query Results with Cursors".beginTransaction. In this release, you must always use explicit transaction control (with the beginTransaction, commitTransaction, and rollbackTransaction methods) when using an updatable cursor and making changes to the database. For information on cursors, see "Manipulating Query Results with Cursors". For information on transactions, see "Managing Transactions".database object, the transaction is rolled back. If the transaction is through a DbPool object, the value of the commitFlag parameter when the connection was established determines whether the transaction is committed or rolled back. For information on establishing connections, see Chapter 8, "Connecting to a Database."http://In these URLs, server represents the name of the server on which you run your application, such asserver.domain/path/file.html
research1 or www; domain represents your Internet domain name, such as netscape.com or uiuc.edu; path represents the directory structure on the server; and file.html represents an individual filename. In general, items in italics in URLs are placeholders and items in normal monospace font are literals. If your server has Secure Sockets Layer (SSL) enabled, you would use https instead of http in the URL.
This book uses the following font conventions:
Last Updated: 10/30/97 12:18:17