Changes between Version 1 and Version 2 of NoJni
- Timestamp:
- 09/04/07 19:07:27 (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NoJni
v1 v2 3 3 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. 4 4 5 It seems, the Java code and the D code can only exist in se qarated processes. JNI cannot do that. An interprocess communication (IPC) is needed.5 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. 6 6 7 7 The requirements for this IPC in TioLink are: