Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:33074
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.226 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=licrDQ6zOSlyrQbQ7tYrTSqFX5Ot1iIBfEgJoKo6LC0gDf82AF7KdaPekdu/+YFuarBLyS14LWLC+dzC2BFypBiBVNJlhahr82Sb7QoisdZ4Tp7AJwEvq4QmDyTlAHIfY4mGawydIokglB7ApalRHW2AfwUAmvFW7blciWKNgaU=
Message-ID: <cd5680a20711100231n7ccdb2c2i878dd5b9f54f057f@mail.gmail.com>
Date: Sat, 10 Nov 2007 13:31:03 +0300
To: "Arend van Beelen" <arend@hyves.nl>
Cc: internals@lists.php.net
In-Reply-To: <e5fac5430711091727n7ce26594scb9b31f1f3babc1e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <e5fac5430711091727n7ce26594scb9b31f1f3babc1e@mail.gmail.com>
Subject: Re: [PHP-DEV] Making parallel database queries from PHP
From: indeyets@gmail.com ("Alexey Zakhlestin")

I would prefer to have some function, which would check, if the
requested data is already available (if it is not, I would still be
able to do something useful, while waiting)

On 11/10/07, Arend van Beelen <arend@hyves.nl> wrote:
> Hi there,
>
> I am researching the possibility of developing a shared library which can
> perform database queries in parallel to multiple databases. One important
> requirement is that I will be able to use this functionality from PHP.
> Because I know PHP is not thread-safe due to other libraries, I am wondering
> what would be the best way to implement this. Right now I can imagine three
> solutions:
>
> - Use multiple threads to connect to the databases, but let the library
> export a blocking single-threaded API. So, PHP calls a function in the
> library, this function spawns new threads, which do the real work. Meanwhile
> the function waits for the threads to finish, and when all threads are done
> it returns the final result back to PHP.
> - Use a single thread and asynchronous socket communication. So, PHP calls
> the library function and this function handles all connections within the
> same thread using asynchronous communication, and returns the result to PHP
> when all communication is completed.
> - Use a daemon on the localhost. Make a connection from PHP to the daemon,
> the daemon handles all the connections to the databases and passes the
> result back to the connection made from PHP.
>
> Can someone give me some advise about advantages of using one approach or
> another? Please keep in mind that I'm hoping for a solution which will be
> both stable and minimizes overhead.
>
> Thanks,
> Arend.
>
> --
> Arend van Beelen jr.
> "If you want my address, it's number one at the end of the bar."
>


-- 
Alexey Zakhlestin
http://blog.milkfarmsoft.com/