Eval IronPython Scripts during ASP.NET Web Request Static motor or not
I would like to create an ASP.NET MVC web application that has extensible logic that does not require re-assembly. I was thinking about creating a filter that had an instance of the IronPython engine. I would like to know: how much is the overhead of creating a new engine during every web request, and would it be better if it supports a static engine? However, if I had to maintain one static engine, what problems could I run into before blocking and scoping the script? Is it possible to have multiple scopes in the same IropPython core so I don't get variable conflicts and security issues between web requests?
a source to share
I've just started using IronPython as an extension point in my ASP.NET MVC application. I have one ipy engine (in a static property) and for every request I create a new scope and execute the script in that scope.
Each area should be independent from other areas, no locking required.
If I have any problems, I'll post it here. However, I don't expect;)
a source to share