From: "Leonardo Santagostini" <lsantagostini@gmail.com>
To: "Eljay Love-Jensen" <eljay@adobe.com>, gcc-help@gcc.gnu.org
Subject: Re: Question about sockets
Date: Mon, 28 Jul 2008 06:37:00 -0000 [thread overview]
Message-ID: <9ab7eeeb0807271351y10708dbftaf20a6f2dccb1ce8@mail.gmail.com> (raw)
In-Reply-To: <C4B1D785.75D6%eljay@adobe.com>
Thanks Eljay !
Yours,
Leonardo
2008/7/27 Eljay Love-Jensen <eljay@adobe.com>:
> Hi Leonardo,
>
> The gcc-help forum is not the correct forum for socket and pthread
> questions. I do not say this to chastise you, rather to inform you that
> faster, more accurate help is likely to come from a more appropriate forum.
>
> That being said...
>
> Your source code is too long. Could you trim it down to a much smaller
> example that exhibits the problem?
>
> Also, when you close your socket, it does not appear that you first did a
> shutdown of the socket.
>
> man 2 close
> man 2 shutdown
>
> You may want to adjust your socket options, such as linger or timeout.
>
> man 2 setsockopt
>
> The CLOSE_WAIT means the remote connection has finished sending data, and
> your side has not yet done a shutdown and close.
>
> The TIME_WAIT means that both sides have close'd the connection, but the IP
> stack is obliged to wait a prescribed time before taking the connection
> down. This is normal, and expected.
>
> Also, your communication may be affected by Nagle's algorithm. In most
> cases, Nagle's algorithm is a good thing. For certain kinds of IP
> communication (what I'd call "chatty" communication), it can introduce
> undesirable latency.
>
> Sincerely,
> --Eljay
>
>
--
Saludos.-
Leonardo Santagostini
prev parent reply other threads:[~2008-07-27 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9ab7eeeb0807262031m1b25ec88r5a425a5c09f96c8d@mail.gmail.com>
2008-07-27 20:51 ` Leonardo Santagostini
2008-07-28 3:23 ` Eljay Love-Jensen
2008-07-28 6:37 ` Leonardo Santagostini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ab7eeeb0807271351y10708dbftaf20a6f2dccb1ce8@mail.gmail.com \
--to=lsantagostini@gmail.com \
--cc=eljay@adobe.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).