Using DBIntegrator
Client for JDBC
[Top] [Prev][Next][Bottom]
Programming Tips
Testing Applets with Netscape Communicator Browser on Web Server Machine
There is a known problem where DBIntegrator Client for JDBC
cannot run JDBC applets with a web browser on the web server computer.
This occurs with Netscape Communicator 4.0.
If you see the error "# Security Exception: Couldn't connect
to 'database' with origin from 'local-classpath-classes'", remove the DBIntegrator
Client for JDBC directory from the CLASSPATH environment variable in the
account running Netscape.
Connecting from an Applet in a Browser
Because of current browser security restrictions,
the Java applet can only connect to data sources on the server from which
it came. This means that DBIntegrator Server has to be running on the same
server as the Web server.
NOTE: The database drivers and DBIntegrator Server must be installed on
the Web server, however your databases can be remote to this server.
Implementing Multi-Threaded Access
DBIntegrator Client for JDBC is thread safe and supports
multi-threaded applications. However, if you are using multi-threaded database
access regularly, it is better to create multiple connections for each
thread. If only one connection is used with multiple threads, only one
thread is allowed to communicate over the network at once. This potential
bottleneck is removed if each thread has its own connection.
[Top] [Prev][Next][Bottom]
csr@unify.com
Copyright © 1998-9, 2002, Unify
Corporation. All rights reserved.