Re: [twsocket] Process pooling for CGI
Is this possible? I want to keep the PHP-cgi.exe process loaded in memory for fast execution. Or is this what ISAPI can only do? Yes, ISAPI is the way to go. ISAPI is just a DLL and stay in memory until you unload it. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Process pooling for CGI
Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, January 12, 2006 2:57 PM Subject: Re: [twsocket] Process pooling for CGI Is this possible? I want to keep the PHP-cgi.exe process loaded in memory for fast execution. Or is this what ISAPI can only do? Yes, ISAPI is the way to go. ISAPI is just a DLL and stay in memory until you unload it. ISAPI is good for ASP but PHP is _not_ thread safe according to php.net. What we need is a way to speed up CGI and the only possible way seems to be process pooling but this is a term I have just made up! Is there such technique? Is there a way to freeze and reinstate a process after a request is answered? I think it would be revolutionary! Best Regards, SZ -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Process pooling for CGI
You may then consider the tiny CGI concept. You create a very small CGI which load very fast (you can build one being less than 150KB and maybe even less than 100KB and still doing useful things). This CGI would load the DLL which would do the real work. If you manage to also load the same DLL from your server, then the DLL will remains always in memory (DLL is shared by all executables provided the load address is compatible with all executables). Instaed of a DLL, you may make the CGI a gateway to your server (or another one), using any IPC you like. That's the concept used by MidWare WebTechnology and his CGIGate module. -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, January 12, 2006 2:08 PM Subject: Re: [twsocket] Process pooling for CGI Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, January 12, 2006 2:57 PM Subject: Re: [twsocket] Process pooling for CGI Is this possible? I want to keep the PHP-cgi.exe process loaded in memory for fast execution. Or is this what ISAPI can only do? Yes, ISAPI is the way to go. ISAPI is just a DLL and stay in memory until you unload it. ISAPI is good for ASP but PHP is _not_ thread safe according to php.net. What we need is a way to speed up CGI and the only possible way seems to be process pooling but this is a term I have just made up! Is there such technique? Is there a way to freeze and reinstate a process after a request is answered? I think it would be revolutionary! Best Regards, SZ -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Process pooling for CGI
Very interesting! Could a generic tiny CGI be written for all interpreters such as PHP, Perl, Python or must we write separate ones for each? How much of the job does your MidWare code do? Is it commercial or free like ICS? Best Regards, SZ - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, January 12, 2006 3:43 PM Subject: Re: [twsocket] Process pooling for CGI You may then consider the tiny CGI concept. You create a very small CGI which load very fast (you can build one being less than 150KB and maybe even less than 100KB and still doing useful things). This CGI would load the DLL which would do the real work. If you manage to also load the same DLL from your server, then the DLL will remains always in memory (DLL is shared by all executables provided the load address is compatible with all executables). Instaed of a DLL, you may make the CGI a gateway to your server (or another one), using any IPC you like. That's the concept used by MidWare WebTechnology and his CGIGate module. -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be - Original Message - From: Fastream Technologies [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, January 12, 2006 2:08 PM Subject: Re: [twsocket] Process pooling for CGI Hello, - Original Message - From: Francois Piette [EMAIL PROTECTED] To: ICS support mailing twsocket@elists.org Sent: Thursday, January 12, 2006 2:57 PM Subject: Re: [twsocket] Process pooling for CGI Is this possible? I want to keep the PHP-cgi.exe process loaded in memory for fast execution. Or is this what ISAPI can only do? Yes, ISAPI is the way to go. ISAPI is just a DLL and stay in memory until you unload it. ISAPI is good for ASP but PHP is _not_ thread safe according to php.net. What we need is a way to speed up CGI and the only possible way seems to be process pooling but this is a term I have just made up! Is there such technique? Is there a way to freeze and reinstate a process after a request is answered? I think it would be revolutionary! Best Regards, SZ -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Process pooling for CGI
Very interesting! Could a generic tiny CGI be written for all interpreters such as PHP, Perl, Python or must we write separate ones for each? To be generic, the CGI should implement ISAPI interface and then can use any ISAPI DLL. Maybe this would make the CGI too big ? Maybe one more DLL layer would maintain small CGI footprint ? How much of the job does your MidWare code do? It translate MidWare request received from the web to something understandable by a standard MidWare appserver. It communicate with the lowest level API to have the smallest exe file possible. Is it commercial or free like ICS? It is commercial. Source available for purchase only. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Process pooling for CGI
Very interesting! Could a generic tiny CGI be written for all interpreters such as PHP, Perl, Python or must we write separate ones for each? To be generic, the CGI should implement ISAPI interface and then can use any ISAPI DLL. Maybe this would make the CGI too big ? Maybe one more DLL layer would maintain small CGI footprint ? Another layer is a good idea since there are not much interpreters, PHP, Perl, Python and maybe Ruby would be sufficient anyway.. How much of the job does your MidWare code do? It translate MidWare request received from the web to something understandable by a standard MidWare appserver. It communicate with the lowest level API to have the smallest exe file possible. Are you sure this idea is not patented? Or maybe you own the patent?? Is the license you provide royalty free? How much is the price you can offer (we can advertise on our web site that we built with your component). (you can answer this privately.) Best Regards, SZ Is it commercial or free like ICS? It is commercial. Source available for purchase only. -- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Process pooling for CGI
Guess this is OT, but check out FastCGI interface. Hello, Is this possible? I want to keep the PHP-cgi.exe process loaded in memory for fast execution. Or is this what ISAPI can only do? Regards, SubZero -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
