From: Luciano Moreira - igLnx <lucianolnx@ig.com.br>
To: Chuck Winters <chuckw@ieee.org>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Efficient UDP Programming
Date: Mon, 23 Aug 2004 10:10:47 -0300 [thread overview]
Message-ID: <4129ECD7.9040305@ig.com.br> (raw)
In-Reply-To: <1093057706.5080.28.camel@nicodemus>
I suggest you to have a fixed size for your header, then you can read
the header that ll say you about the rest of data following the header.
Luciano
Chuck Winters escreveu:
>Is there anyway of reading some data from a UDP socket without removing
>it from the received queue? What I need to do is read in the header
>from a packet to determine how large of a memory chunk I need to
>allocate.
>
>Thanks,
>Chuck
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
prev parent reply other threads:[~2004-08-23 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 3:08 Efficient UDP Programming Chuck Winters
2004-08-23 13:10 ` Luciano Moreira - igLnx [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=4129ECD7.9040305@ig.com.br \
--to=lucianolnx@ig.com.br \
--cc=chuckw@ieee.org \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).