Re: [jruby-dev] jruby.launch.inproc should default to false

2008-03-14 Thread Nick Sieger
On Thu, Mar 13, 2008 at 12:32 PM, Matt Fletcher <[EMAIL PROTECTED]> wrote: > I brought this up in IRC the other day; I was encouraged to post this > to the mailing list instead of JIRA. > > As for status quo: I'm not sure what you mean by that. As far as I > know, you always get a new process in

Re: [jruby-dev] jruby.launch.inproc should default to false

2008-03-13 Thread Matt Fletcher
I brought this up in IRC the other day; I was encouraged to post this to the mailing list instead of JIRA. As for status quo: I'm not sure what you mean by that. As far as I know, you always get a new process in MRI, so that sounds like the status quo to me. I don't disagree with your arg

Re: [jruby-dev] jruby.launch.inproc should default to false

2008-03-13 Thread Nick Sieger
On Mar 11, 2008, at 3:53 PM, Matt Fletcher wrote: This is an opinion piece; it is meant to convince you that the jruby.launch.inproc property should default to false. Summary: Trying to run new jruby or ruby instances in the same process is dangerous; the jruby.launch.inproc property contro

[jruby-dev] jruby.launch.inproc should default to false

2008-03-11 Thread Matt Fletcher
This is an opinion piece; it is meant to convince you that the jruby.launch.inproc property should default to false. Summary: Trying to run new jruby or ruby instances in the same process is dangerous; the jruby.launch.inproc property controls this behavior and should prefer safety and accu