Network buffering question
- From: Till Crueger <TillFC@xxxxxxx>
- Date: Tue, 29 Aug 2006 00:18:29 +0200
Hi,
I hope this is the best newsgroup for this topic. I looked around, but I
couldn't find any more specific newsgroups.
I am working on some network code right now. For help I am using "Beej's
Guide to Network Programming". Now I stumbled upon the chapter about data
encapsulation. I get the point that you should send across the Network
some information about how much data you have been sending, so you can
reconstruct the packets correctely. So far I think I got everything.
However then he says that you need to make your buffer twice as large as a
single packet, because you might actually read past the packet you are
trying to handle at the moment. Since you can tell recv() how much you
want to recieve couldn't you just make sure this wont ever happen? I would
have tried something like this:
read size information
check if everything was recieved
read the rest (let recv() know how much to read)
Or is there some problem to this, so you actually need to use bigger
buffers or circular buffers?
Thanks for your help,
Till
--
Please add "Salt and Pepper" to the subject line to bypass my spam filter
.
- Follow-Ups:
- Re: Network buffering question
- From: Alex Fraser
- Re: Network buffering question
- From: Alex Fraser
- Re: Network buffering question
- From: David
- Re: Network buffering question
- From: Scott McPhillips [MVP]
- Re: Network buffering question
- Prev by Date: Re: Code Comprehension
- Next by Date: Re: Fibonacci implementation
- Previous by thread: Fibonacci implementation
- Next by thread: Re: Network buffering question
- Index(es):
Relevant Pages
|