better Java IPC@Linux tactic: (a) java.nio File API on /dev/shm or (b) JNI to shmctl(2)? -
we want write java 7 program boot (via 2 cmd line invokes) 2 separate jvm process instances. want these 2 processes communicate each other using native linux kernel shared-memory ipc resources.
does have insight of these 2 approaches may have more merit?
- use java.nio.* api on /dev/shm
- use jni bridge c++ code makes native shmctl() system calls
?
i vote "nio , /dev/shm".
but before making final decisions, should consider other options, including clip:
sockets, message queues , named pipes other ipc methods wouldn't dismiss out-of-hand. imho...
Comments
Post a Comment