Message-Id: <199704251823.OAA00410@u4-138.openmarket.com> To: Nat Holder <firstname.lastname@example.org> Subject: Re: multiple processes on remote host In-Reply-To: Your message of "Wed, 23 Apr 1997 12:55:52 CDT." <Pine.NXT.3.95.970423110734.5261G-100000@litoria> Date: Fri, 25 Apr 1997 14:23:03 -0400 From: Stanley Gambarin <gambarin@OpenMarket.com> To provide the support for multiple instances of the fastcgi-application running on the remote machine, some "hacking" will be required. The mod_fastcgi has inside a code to support the concept session affinity, where each instance of the same FastCGI application class is differentiated from the next. However, the Apache does not provide support for this concept. So, this is one method that you may employ to get the desired functionality: - look at ConfigureTCPServer() function in mod_fastcgi, at place where AFFINITY is defined. You will see that each instance of the application will be listening at the different port, starting at the base port number. You can use that code to allow for multiple instances of the remote application. - you will need to modify FastCGIHandler() function at the place where the connect() function is called in such a way that if the connect fails (do non-blocking connect, then select and see if timeout occurs), you can construct a new IpcAddress (with the next port number in sequence) and try it again. This is not an essential functionality, but an additional feature, so I will not implement it, but you can do it relatively easy and provide the diffs for the next version of the mod_fastcgi module. Hope that was of some help. Stanley.