> Maybe I could stick the VM handle into a thread local variable on the main > thread ? If there is no value, it's a new VM, if there is one, you add to > it.
Sounds good. Or, put the global variable in Java space? Or, a new attribute in "sys", called "JCC_Env"? > The problem with that approach is that there are bunch of things about > the VM you can't change once it's started and so there is likely to be a > certain amount of coordination required between your modules so that they > can all share the VM. For example, max stack and heap sizes come to mind. Well, that's not too bad, I always max them out. But it would be nice to have accessors for them, so that subsequent modules could check them. Bill _______________________________________________ pylucene-dev mailing list [email protected] http://lists.osafoundation.org/mailman/listinfo/pylucene-dev
