Re^2: can Perl-CGI run persistently on Windows 2008 with IIS 7.5? how?

The web server called a small cgi mod-perl script ( ~200 lines ) that sent the request to the persistent process using sockets, wait for the response, and then sent that response to the webserver.

How does that differ from fastcgi? (That's a real question not an admonishment. I don't do webstuff :)

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Comment on Re^2: can Perl-CGI run persistently on Windows 2008 with IIS 7.5? how?

Replies are listed 'Best First'.
Re^3: can Perl-CGI run persistently on Windows 2008 with IIS 7.5? how? by flexvault (Monsignor) on Aug 03, 2012 at 10:21 UTC
Hello BrowserUk, How does that differ from fastcgi? Since you know that I support a lot of different nix type systems, I found it easier to define the HTTP, javascript, etc. differences as well as the different forks per core per server. Even different Linux distributions needed tinkering when using the 'same' web-server. I did try fastcgi and pperl(persistent perl) and a few more. In concept they do exactly what I did, but the 'devil is in the detail'. For example, I used pperl on a server that I could 'ssh' to and run persistent scripts, but if I connected the 1st time as 'aixterm' and then later as 'wyse60', all hell broke out. Now maybe an pperl expert would tell me "just ...", but I just couldn't find the information in the documentation. At that time in my Perl development, I didn't know about PM! Thank you "Well done is better than well said." - Benjamin Franklin*	[reply]
Re^3: can Perl-CGI run persistently on Windows 2008 with IIS 7.5? how? by Anonymous Monk on Aug 03, 2012 at 09:52 UTC
:)(I'm guessing) Its written in pure-perl, and (probably) ad-hoc without an accompanying RFC (like FastCGI/PSGI)	[reply]