Sieve inetBench - release 20010825

Last Change: August 25, 2001

1) Installing Software

To run the Sieve inetBench, you need to have the Java Runtime Environment 1.4 or later. If you do not have it, you can download the latest Runtime Environment from Sun.

Dynamically compiled s4w components require the Jikes Bytecode Toolkit from IBM.

If you wish to compile your own version of Sieve, you will also need:

  1. the Java Development Kit 1.4 or later from Sun
  2. the Jikes compiler 1.14 or later from IBM
  3. GNU make 3.79.1 or later from the GNU Project
    If you are running Windows, you can obtain GNU make as part of the Cygwin library
2) Obtaining Sieve

Sieve is currently available in source and pre-compiled forms.

To use the pre-compiled version of Sieve:

  1. Download the sieve.jar file to your local hard drive.
  2. Unpack sieve.jar with jar xvf sieve.jar
To compile your over version of Sieve from source:
  1. Download the sieve-src.jar file to your local hard drive.
  2. Unpack sieve-src.jar with jar xvf sieve-src.jar
  3. In Makefile.config set the value of JDK_DIR to the location of your Java Development Kit installation
  4. In Makefile.config set the value of JIKES_DIR to the location of your Jikes installation
  5. In Makefile.config set the value of JIKESBT_DIR to the location of your Jikes Bytecode Toolkit installation
  6. Run make
3) Running Sieve

Because Sieve uses features not normally granted to applets, you must use a security policy file. An example policy file is provided as java.policy. To use this example file, change the URI in the first line

grant codeBase "file:/sieve/" {
to the URI at which Sieve is installed. Alternatively, you can write your own policy file. When using dynamically compiled components, you will also need to change the URI in the line
grant codeBase "file:/usr/local/jikesbt/" {
to the URI at which the Jikes Bytecode Toolkit is installed.

When running Sieve, you will need to direct your Java virtual machine to use the policy file you have written. For example, when using the java command you would use:

java -Djava.security.policy==java.policy
and when using the appletviewer command you would use:
appletviewer -J-Djava.security.policy=file:java.policy
Be sure that your CLASSPATH has the location of the Jikes Bytecode Toolkit and the location of the Java Runtime jar file in it when using dynamically compiled components.

Scripts have been provided to automate this process. When running the Sieve server, you can use:

runserver $1 $2
where $1 is the directory to write temporary files and $2 is the address for the server to bind to. When running the Sieve client, you can use:
runclient $1
where $1 is a file URI of an HTML page that launches the Sieve client. Two examples are user.html and s4w.html in the base directory of Sieve.

Example: runserver /tmp 127.0.0.1
Example: runclient user.html

IMPORTANT: If you are using Windows 95 or  98 ...

...and you see painting problems like this:
interface looks bad

...instead of this: interface as it should look (no painting problems)

This is a bug in Java's user interface implementation, not in Sieve. This bug is known by Sun and as of version 1.2.2  of Java (the latest when this page was written) it was not fixed. It occurs when you are using a non-default windows theme that changes the cursor. If you find this behaviour too distracting, the only solution is to set the cursor back to its default setting.

Any comments, doubts or questions? Write to Dr Cliff Shaffer (shaffer@shaffer.cs.vt.edu)