Because DJ is transparent to the Java program, the programmer does not need to know anything about the network of computers that the program will be run on. This allows for future features such as dynamic node acquisition, to enable a computation to grab as many available nodes on a network as possible. I am not working on dj currently. It has been a while since I have last updated this page. In that time, a lot has changed.
DJ now runs on single nodes, and includes support for multithreading.
DJ is close to running on multiple nodes. Since the Java Virtual Machine is a stack oriented machine, I decided that it was important to have a well designed stack, both for reliability and for performance reasons. Linking in the native method libraries is a little troublesome. Future Projects Despite the fact that I haven't even completed the first version of DJ, I still have come up with some ideas for future projects. It may be better to group threads that require synchronization, or access to common objects, together on the same node, than it would be to distribute them.