> If we cannot use something like Unix Domain sockets then probably a > randomly spawned password by client (which then spawns initial server > instance) which then gets stored securely to a file in users home > directory may do the trick. The successive calls would pass this > secret as proof of ownership. The file that stores the password in > would be chmod'd so other users cannot read it. This file could also > store the pid of the server so we can make sure it did not die at some
This (per-launch key) sounds like an improvement over what we have now. > point. Combine that with Jochen's spawn on first command logic and > there could be an ENV to main startup lang (jruby) script for people > who don't mind having background server stick around for a while in > case the person will do several invocations in a short period of time. There are different situations I ran into where I wanted the server to stick around for much longer than a minute or two. One was where the kinds of operations I was running could take advantage of runtime optimization, and the other was where the startup process was very long (long chain of dependencies and injections). Having this be configurable seems like a plus for me--I can spare the memory more than the time involved. Patrick --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
