|
|
also be run on Unix workstations. The archiving procedures differ in that Netscape's signtool
will create and place the signed applet code in a Java archive (.jar file) whereas Microsoft's
signcode operates on an existing proprietary cabinet archive (.cab file) created with their
cabarctool. Hence, the mechanism for retrieving the appropriate signed applet differs for the
two major browsers, although the different tags can be combined in the same piece of HTML
code so that each browser can select the appropriate archive :
|
|
|
|
Example 1: The Chemical Object Store (COS). COS, as noted above, provides a
distributed client object in the form of a Java applet which invokes methods for interrogating a
remote object database and returning a chemical data object7, which may reformatted into a
PDB format co-ordinate file for display purposes or saving to the local filestore. We believe
this to be the first published chemical application of such an authenticated distributed
computing technique. For use within a local environment, the user should have access to their
local file store in order to save the file. The client should also be able to retrieve files from the
local store to be able in turn to submit them to the remote database. This means that the
applet client must have access to Java FileDialog classes to provide this functionality. Such
classes are included with the Windows 95 version of the Netscape browser's Java class
library, and client access to them is made available if the applet is deemed trusted using the
authentication procedures described above. We note that the Macintosh version of the
Netscape browser (Version 4.5 was the latest available to us at time of writing) does not yet
implement these FileDialog classes. Vexingly, the use of such FileDialog classes appears not to
be permitted in Internet Explorer, even with a valid digital certificate.
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
