On Thu, Mar 25, 2010 at 12:13 PM, Peter Lind <peter.e.l...@gmail.com> wrote:
> On 25 March 2010 20:09, Tommy Pham <tommy...@gmail.com> wrote:
>> On Thu, Mar 25, 2010 at 12:02 PM, Peter Lind <peter.e.l...@gmail.com> wrote:
>>> On 25 March 2010 19:37, Tommy Pham <tommy...@gmail.com> wrote:
>>>> On Thu, Mar 25, 2010 at 3:55 AM, Per Jessen <p...@computer.org> wrote:
>>>>> Tommy Pham wrote:
>>>>>> On Thu, Mar 25, 2010 at 1:46 AM, Per Jessen <p...@computer.org> wrote:
>>>>>>>> * If you could implement threads and run those same queries in 2+
>>>>>>>> threads, the total time saved from queries execution is 1/2 sec or
>>>>>>>> more, which is pass along as the total response time reduced.  Is it
>>>>>>>> worth it for you implement threads if you're a speed freak?
>>>>>>> Use mysqlnd - asynchronous mysql queries.
>>>>>> You're assuming that everyone in the PHP world uses MySQL 4.1 or
>>>>>> newer.  What about those who don't?
>>>>> They don't get to use threading, nor asynchronous mysql queries.
>>>>> Come on, you're asking about a future feature in PHP 7.x , but would
>>>>> like to support someone who is seriously backlevel on mysql??
>>>>> --
>>>>> Per Jessen, Zürich (16.9°C)
>>>> I'm not talking about MySQL 4.0 or older.  I'm talking about other
>>>> RDBMS.  I think you should open your eyes a bit wider and take a look
>>>> at the bigger picture (Firebird, MSSQL, Oracle, PostgreSQL, etc).
>>> http://www.php.net/manual/en/function.pg-send-query.php
>>> Looks to me like the PHP postgresql library already handles that. Not
>>> to mention: you're not presenting an argument for threads, you're
>>> presenting an argument for implementing asynchronous queries in the
>>> other DBMS libraries.
>>> Of course, the problem could also be solved by introducing threads in
>>> PHP. I'd personally guess modifying DBMS libraries would be less
>>> costly, but as I haven't been involved in writing the PHP code my
>>> guess isn't worth much.
>>> Regards
>>> Peter
>> I'm presenting the argument for threading.  Per is presenting the work
>> around using asynchronous queries via mysqlnd.  I did read that link a
>> few days ago, "Although the user can send multiple queries at once,
>> multiple queries cannot be sent over a busy connection. If a query is
>> sent while the connection is busy, it waits until the last query is
>> finished and discards all its results."  Which sounds like threads ->
>> multiple connections to not run into that problem.
> Have you looked into what it would cost in development to improve the
> library? Have you compared that to the cost in development to
> introduce threads into PHP? No, I don't think you're presenting the
> argument for threading - but I don't expect you to see it that way.

Aren't all feature requests must be analyzed the same way?  Example,
namespace, how many of us actually uses it now when there is an
alternative solution- subfolders - that we've been using since who
knows how long.  I don't know if threads was asked a feature prior
namespace was implemented.

PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to