Re: howto receive and *understand* via UDP
- From: dj3vande@xxxxxxxxxxxxxxxxxxxxxxxxxxx
- Date: Thu, 22 Nov 2007 20:09:14 +0000 (UTC)
In article <d9a92895-751c-4a59-a253-7df7204467e7@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Doug <DougTheScot@xxxxxxxxxxxxxx> wrote:
dj3va...@xxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
In article <98d642a2-202f-48e8-b416-38fd15504379@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Doug <DougTheScot@xxxxxxxxxxxxxx> wrote:
This is all off-topic, I know, but since others are joining in...
Most of the others are giving pointers to better places to look for
information, not incorrect answers.
Fair enough.
I saw something interesting, but was in a rush (and a bit bored from
the this afternoon) and brain dumped without thinking. You're right,
it was in the wrong place. For that I apologise to the group.
Do you have to be so impolite about it, though? Oh well.
"Impolite" is not the word you're looking for. "Blunt", perhaps.
And no, it wasn't strictly required, but neither was it inappropriate.
Remember that the OP is discussing UDP; there are no size issues*
here; datagram messages are delivered singly and completely (or not at
all). (The size is given from the return code from recv/recvonly.)
* not quite true, you need to have provided a buffer big enough for
the incoming datagram; MTU size should be fine.
There is at least one factual error in the preceding quoted material.
Had it been posted in an appropriate newsgroup, it would have been
topical to say what that error is and provide correct information, and
there would have been people with the relevant knowledge to do so (and
to correct any errors in the correction).
I'm interested to know what the error is. But I'm guessing you won't
tell me here.
You guess correctly, but:
Fair enough; it's clear you're not at all actually
interested in helping anybody. You would be one of those net nannies.
Your assumed reason is incorrect. I'm not a net nanny, merely a C
programmer with a fanatical obsession with correctness and a healthy
respect for the purpose behind topicality guidelines.
The reason why I won't say here is because I'm not exactly an expert
myself, and my conclusion that it was an error was a result of thinking
"that doesn't look right" followed by a few minutes of looking up
details. If I were to say what I thought about it here, nobody
(including me) would have any guarantee of either the correctness of my
statement or the kind of peer review that would result in corrections,
and therefore nobody would have any reason to give that any more weight
than they would give what you said.
dave
.
- Follow-Ups:
- Re: howto receive and *understand* via UDP
- From: Doug
- Re: howto receive and *understand* via UDP
- From: Doug
- Re: howto receive and *understand* via UDP
- References:
- Re: howto receive and *understand* via UDP
- From: Doug
- Re: howto receive and *understand* via UDP
- From: dj3vande
- Re: howto receive and *understand* via UDP
- From: Doug
- Re: howto receive and *understand* via UDP
- Prev by Date: Re: multi-character constant
- Next by Date: Re: why the usage of gets() is dangerous.
- Previous by thread: Re: howto receive and *understand* via UDP
- Next by thread: Re: howto receive and *understand* via UDP
- Index(es):
Relevant Pages
|