comment on

Another way to do it...

Here's some client code for a slower responding socket server, or when all the data doesn't show up at once, due to other issues. It sends a chunk, and waits for a response, up to N loops. Small sleeps might be safer than just looping, but hey, everyone works differently. You also could add checks for some termination sequence, or checks for the chunk meeting a fixed size requirement.

--bibo

my $indata;
my $remote = IO::Socket::INET->new(
  Proto    => "tcp",
  PeerAddr =>'127.0.0.1' ,
  PeerPort => $self->{'30000'},
);
if( defined($remote) ) {
  my $readsize;
  print $remote  $bigdata;          
  my $done = 0;
  my $zreads =0;
  while (! $done) {
    my $tempdata="";
    $tempdata = <$remote>;
    $readsize = length $tempdata;
    $zreads++ if ($readsize == 0);
    $done = 1 if ($zreads > 30);
    $in_data = $in_data . $tempdata;
    $done = 1 if ($tempdata eq "\n");
  }
  close $remote;
}
[download]

In reply to Re: Perl socket handling problem by bibo
in thread Perl socket handling problem by HumanProgrammer

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.


XP is just a number
	PerlMonks