= Why does Java JNI not work for TioLink? =

D and Java are both using a garbage collector. These GCs are suspending threads at their will and awake them if they are done. With JNI both share the same native threads, but the D GC does not know the Java GC nor vice versa. This is why they have to conflict sooner or later. I see no solution for this.

It seems, the Java code and the D code can only exist in separated processes. JNI cannot do that. An interprocess communication (IPC) is needed.

The requirements for this IPC in TioLink are:
 * cross language Java, D
 * available for all D plattforms Win32, Linux, Max OSX
 * good performance

Alternatives
 1. pure sockets/tcp[[br]]
   [-] reinvent the wheel[[br]]
 2. [http://www.omg.org/gettingstarted/corbafaq.htm Corba][[br]]
   [-] too much to implement[[br]]
   [-] performance[[br]]
 3. [http://dbus.freedesktop.org D-Bus] (see [http://www.dsource.org/projects/dbus-d/ DBus-D])[[br]]
   [+] meets the requirements[[br]]