Received: from superfly.archi-me-des.de ([62.8.212.177]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g11CtOl60544 for ; Fri, 1 Feb 2002 07:55:24 -0500 (EST) (envelope-from frank@joerdens.de) Received: (from frank@localhost) by superfly.archi-me-des.de (8.9.3/8.9.3) id NAA01273; Fri, 1 Feb 2002 13:55:19 +0100 Date: Fri, 1 Feb 2002 13:55:19 +0100 From: Frank Joerdens To: Marco Colombo Cc: Frank Bax , pgsql-php@postgresql.org Subject: Re: apache-php-postgresql connection question Message-ID: <20020201135519.D910@superfly.archi-me-des.de> References: <3.0.6.32.20020131162351.01e36e00@pop6.sympatico.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i In-Reply-To: ; from marco@esi.it on Fri, Feb 01, 2002 at 01:04:44PM +0100 X-Subliminal-Message: Use Linux! Use Linux! X-Archive-Number: 200202/3 X-Sequence-Number: 909 On a slightly different note, does anyone know whether this problem is maybe solved entirely once PHP is fully multithreaded and works with Apache 2, which is also multithreaded? Or if you can use PHP with AOLServer to benefit from AOLServer's multithreadedness and connection pooling capability? Or if you can use connection pooling through some Java mechanism if you build PHP as a servlet to run on top of a JVM as described at http://www.php.net/manual/en/ref.java.php: -------------------------- snip -------------------------- sapi/servlet builds upon the mechanism defined by ext/java to enable the entire PHP processor to be run as a servlet. The primary advanatage of this from a PHP perspective is that web servers which support servlets typically take great care in pooling and reusing JVMs. -------------------------- snap -------------------------- Dunno how that might work, through JDBC maybe? Regards, Frank