On 11/3/06, Christopher Baus <[EMAIL PROTECTED]> wrote:
The reload IronPython functionality I think needs to be there for completeness but I feel the single long running IP instance should be enabled by deafult in the example web.config.
Let me look into this
I'm beginning to wonder if we really need the reload IronPython
functionality in WSGI. It adds some complexity for not a lot of real
gain. I thought one reason for reloading the interpreter would be to
reload all the modules, but that can be done via WSGI middlewear.
The reload IronPython functionality I think needs to be there for completeness but I feel the single long running IP instance should be enabled by deafult in the example web.config.
Also I ran into a problem with the flup session middlewear. It uses the
third, exec_info, parameter of start_response, which isn't supported in
our current implementation. I will admit I am not totally sure how to
properly implement this. According to the pep it has something to do with
not sending the headers of the response twice.
Let me look into this
http://baus.net/
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
