Thanks. This was exactly the kind of feedback I was looking for. I wish you could have said that this would be trivial, but you can't get everything :)
I also think that this conversion is something that probably has to be done, but management buy-in is going to be difficult. We have a limited amount of resources so arguing for using good chunk of our available time on this is going to be difficult. I will probably try to get it to work more or less flawlessly on a small and recently implemented part of the application as a proof of concept. Then I can use that to showcase how much more responsive the application feels and convince them to do the conversion for the rest of the application as well. Given that I can actually get it to work of course.
BTW I am still interested to hear others experience with doing this type of conversion and on getting it to work both under CGI and FastCGI.
In reply to Re^2: Getting pure CGI application to run under FastCGI on IIS
by oyse
in thread Getting pure CGI application to run under FastCGI on IIS
by oyse
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |