Edit report at http://bugs.php.net/bug.php?id=12802&edit=1

 ID:                 12802
 Comment by:         tyra3l at gmail dot com
 Reported by:        cheapsalsa at yahoo dot com
 Summary:            gethostbyname/gethostbyaddr timeout
 Status:             Assigned
 Type:               Feature/Change Request
 Package:            *General Issues
 PHP Version:        4.0CVS-2001-08-16
 Assigned To:        pajoye
 Block user comment: N
 Private report:     N

 New Comment:

can I access that implementation from userspace right now?

if there is a way, then it's fine for me as is, but I wouldn't dare to
change the 

current implementation of those functions.

so maybe the best would be to add new userspace functions for the async
behaviour.



Tyrael


Previous Comments:
------------------------------------------------------------------------
[2010-11-19 01:07:41] [email protected]

We have an implementation, only a matter of using it instead of get*. I
have some patch for that, adding some features for the DNS APIs. It
should be easy to modify this function while being at it.

------------------------------------------------------------------------
[2010-11-19 00:53:25] tyra3l at gmail dot com

maybe we could use some non-blocking dns library?

http://c-ares.haxx.se/



Tyrael

------------------------------------------------------------------------
[2010-11-19 00:05:31] [email protected]

For the record, it is not possible to do it in PHP. These functions are
implemented by the operating systems. Without creating a thread for the
get* hosts, we won't have any control on the timeout.

------------------------------------------------------------------------
[2010-03-04 16:34:30] tyra3l at gmail dot com

bump

------------------------------------------------------------------------
[2009-03-04 19:19:12] adifranco at tagged dot com

Any intent to fix this?  This kind of indeterminism is very crippling to
trying to use these functions in a feature that interacts with the user.

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    http://bugs.php.net/bug.php?id=12802


-- 
Edit this bug report at http://bugs.php.net/bug.php?id=12802&edit=1

Reply via email to