soka. hmm. but... I tested this once; program did two HTTP requests, with one that closed the socket after it found what it wanted from response headers, other read it all through. The first one was faster, so I assumed that somehow killing the socket saved me time. Guess it was just coincidence, I didn't really repeat the test, it was only a side effect.

Now, forgive my ignorance on TCP issues (I did tutorial on it but it mostly dealed with ACK/SYN ping-pong), but how does it decide when to download, then? When I open a socket, I automatically start sucking in data to the buffer? So if I opened a socket to connection that would just keep feeding and feeding data, and left the socket alone, I'd get buffer overflow eventually?-)


In reply to RE: RE: RE: Re: reading from sockets by kaatunut
in thread reading from sockets by $CBAS

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.