For the socket stuff, you can also use the zmq addon. On Wed, Jul 25, 2018 at 6:41 AM, Raul Miller <[email protected]> wrote:
> So, ... > > Here is my understanding of these mechanisms in the context of Linux: > > JDo is designed to work within a single process. You should be able to have > several J interpreters loaded in the same process, but when running one, > you wouldn’t be running the other(s). > > You might be able to work around this using clone() instead of fork, but: > > (1) you still need to ensure sequential operation (locks or semaphores or > whatever) when using JDo() or accessing another instance’s variables > (unless you don’t mind inconsistent results and/or crashes). > > (2) There might be other, similar issues (perhaps revolving around > input/output). This isn’t something that has had a lot of testing. > > If I were tackling a project like what you have described, I would use > sockets to communicate between processes (and I think the socket listeners > would essentially be the J interactive prompt). > > Thanks, > > — > Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
