Re: sockaddr_in() timeout or asynchone call ?
- From: Uri Guttman <uri@xxxxxxxxxxxxxxx>
- Date: Fri, 24 Mar 2006 16:57:40 -0500
"JG" == Jim Gibson <jgibson@xxxxxxxxxxxxxxxxx> writes:
JG> The choice to prevent a program blocking on I/O usually involves
JG> either non-blocking I/O (polling) or asynchronous I/O (e.g, the
JG> select statement or forking/threading). Both have their
JG> complications.
you are conflating several things there. the blocking nature of the
socket has nothing to do with whether you use select on it. and select
has nothing to do with forking/threads. and async i/o can means using
the OS's async i/o ops or an event loops that supports it or even using
threads. so you can pretty much mix and match all of those things and
you don't have an either/or situation.
but i agree with your main assessment, sockaddr_in just does some simple
IP address munging and should never block. the OP is confused or
misunderstood something.
uri
--
Uri Guttman ------ uri@xxxxxxxxxxxxxxx -------- http://www.stemsystems.com
--Perl Consulting, Stem Development, Systems Architecture, Design and Coding-
Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
.
- Follow-Ups:
- Re: sockaddr_in() timeout or asynchone call ?
- From: Asterbing
- Re: sockaddr_in() timeout or asynchone call ?
- References:
- sockaddr_in() timeout or asynchone call ?
- From: Asterbing
- Re: sockaddr_in() timeout or asynchone call ?
- From: Jim Gibson
- sockaddr_in() timeout or asynchone call ?
- Prev by Date: Re: Great JAPH (was Re: Creating Graphs Dynamically with Perl)
- Next by Date: Re: 533: error: syntax error before "void"
- Previous by thread: Re: sockaddr_in() timeout or asynchone call ?
- Next by thread: Re: sockaddr_in() timeout or asynchone call ?
- Index(es):
Relevant Pages
|