The best is to host the scriptingruntime in global.asax A script scope is something that you can think of as a unit of runnable script (1 or more files) so in a web scenario I'd say that a scriptscope is scoped to a request.
For IronRubyMVC it works like this: Global.asax initializes the ruby engine and stores it in a static var The ruby engine initializes the runtime and scriptengine http://github.com/casualjim/ironrubymvc/blob/master/IronRubyMvc/Core/RubyMvcApplication.cs http://github.com/casualjim/ironrubymvc/blob/master/IronRubyMvc/Core/RubyEngine.cs#L389 hope this helps otherwise give us some more specific questions --- Met vriendelijke groeten - Best regards - Salutations Ivan Porto Carrero Blog: http://flanders.co.nz Twitter: http://twitter.com/casualjim Author of IronRuby in Action (http://manning.com/carrero) On Tue, Feb 2, 2010 at 2:08 PM, Marco Parenzan <marco.paren...@libero.it>wrote: > Dear All, > > are there any advices about hosting DLR under ASP.NET for scripting? (not > for views!)? > Where hosting ScriptingRuntime, ScriptingEngine? > As static variables in Global.asax? In Application? > Where hosting ScriptingScope? In Session? Destroy and reistantiate at each > call? > > I have to develop an ASP.NET MVC application, with no serious performance > issues, but I don't want to abuse... > > Thanks in advance > > Marco Parenzan > > _______________________________________________ > Ironruby-core mailing list > Ironruby-core@rubyforge.org > http://rubyforge.org/mailman/listinfo/ironruby-core >
_______________________________________________ Ironruby-core mailing list Ironruby-core@rubyforge.org http://rubyforge.org/mailman/listinfo/ironruby-core
