Re: nonblocking connect and threads
| From: | Sascha Schumann | Date: | Sun, 03 Sep 2000 20:18:47 +0000 |
| Subject: | Re: nonblocking connect and threads | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-31836@lists.php.net to get a copy of this message | ||
On Sun, 3 Sep 2000, Stig Venaas wrote:
> On Sun, Sep 03, 2000 at 09:17:14PM +0200, Sascha Schumann wrote:
> > On Sun, 3 Sep 2000, Stig Venaas wrote:
> >
> > > I see that nonblocking connects are implemented using nonblocking
> > > I/O. I wonder if I should use threads instead, I'm not sure how
> > > portable threads are, are most implementations similar to Pthreads?
> >
> > Why wouldn't you want to use non-blocking I/O?
>
> I think nonblocking I/O might be less standardized than threads (you
> guys probably know more about this than me)
Non-blocking I/O is well standardized. "Threads" is a
concept, it cannot be standardized.
> and I don't see how to timeout the resolving without threads.
Unix: Use the resolver(3) interface
Win32: Use WSAAsync* functions
So, we need some level of abstraction here, since there is no
portable solution to the problem (unless someone develops an
asynchronous resolver under a suitable license).
- Sascha