comment on

For checking the state of a socket, I prefer to the system call version of select RBITS, WBITS, EBITS, TIMEOUT. It requires a little more setup using vectors and such, but the result is finer control, IMHO. -ben (perlcapt)

# socket is already setup, and client accepted
# set up masks for use by select
my ($rin,$win,$ein) = ("","","");
my ($rout,$wout, $eout) = ($rin, $win, $ein);
vec($rin, fileno($client),1) = 1;
vec($win, fileno($client),1) = 1;
$ein = $rin | $win;

# -- code deleted --

# wait until the client is ready for writing
if(select(undef,$wout = $win,undef,$timeout)) {
   # <$client> or sysread
    }
# -- code deleted --
# or


# wait until client is ready for writing to
if(select(undef,$wout=$win,undef,$timeout)) {
   # print client or syswrite
}
[download]

In reply to Re: Trapping socket error in client when server goes away by perlcapt
in thread Trapping socket error in client when server goes away by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Keep It Simple, Stupid
	PerlMonks