[IronPython] Multiple Engines and IronRuby

[Michael Foord]

Hello all, Sorry to harp on about multiple engines, but it looks like the ability to host multiple engines may be much more important to IronRuby than it is to IronPython:     However, the DLR holds a sting in the tail for Rails deployment. The 'standard' (again quoting Ola, and hopefully not     mangling what he said too badly) way of deploying a Rails application with JRuby is to have several mongrel processes     connecting to several JRuby engines hosted within a single JVM instance. No need to start a new virtual machine to     handle another request.      With the DLR (and at least IronPython 2), this isn't possible. IronPython 1 supported multiple Python engines (which      you could host within an IronPython application). This has gone from IronPython 2, which is a shame as currently     Resolver uses this feature! We hope that pressure from the Ruby community will force the DLR team to rethink the     'single engine' issue... >From conversations with Ola Bini, I've written it up here:     http://www.voidspace.org.uk/python/weblog/arch_d7_2007_06_02.shtml#e736 :-) Michael Foord http://www.voidspace.org.uk/ironpython/index.shtml

_______________________________________________
users mailing list
users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com