I will take a look at the mod_perl documentation. Thanks for the tip.

For the specific issues I have had with the CGI object and the CGI parameters, I think it would be easier to post each of them in separate thread if I decide to do the conversion. That would make them easier to find using Search later as well.

Now I am more interested in getting an idea of the scope of the effort of getting a CGI application to run under FastCGI and if there are important issues to keep in mind (in addition to the globals and the closures that you already mentioned), if running FastCGI on IIS is common and if it is possible to have a application run but under CGI and FastCGI without doing too much work to keep the application running under both environments.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.