> However, my "silly" solution (suggested earlier) is indeed robust – > and I've just been doing experiments on this: > > $ jconsole -js a=.23 b=.3 "echo a*b" "exit''" >
Thanks for elaborating Looks like a solid, simple solution to me. I wouldn't touch the sockets unless there was too much overhead in getting J back to the state desired to execute against (e.g. loading a large file) I've also used the 'silly' solution with J in a webapp awhile back to avoid mucking around with sockets and threads. The problem with the daemon approach is making sure the daemon is alive ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
