Re: Unnecessary Frame Fragmentation using beepcore-c?

David C Niemi wrote:
 > It seems almost as though the frame sizes are random, although it does
 > settle into a rhythm of 3568 + 528 byte frames about halfway through a 1
 > MB file.  The entire file does always make it intact, eventually.

It's been a long time since I worked on this, but I suspect that what's 
happening is you're buffering up frames faster than they can be sent, 
and every time the beepcore-c library gets a SEQ, it's sending as much 
as it can. That is, the caller is reading less than 4K at a time, 
sending a SEQ, and at that point you're sending the next chunk, however 
big fits.

Try watching the SEQ messages going back and forth and see if they match 
the packet sizes.

-- 
Darren New, San Diego CA USA (PST)
Don't take home left-over tripe.
   It'll just digest itself before
     you get around to eating it.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf