Re: Unnecessary Frame Fragmentation using beepcore-c?

well, beepcore-c needs work. it shouldn't get into silly window
syndrome.
    
what beepcore-tcl does is this:
    
    - channel zero gets an explicit reservation of 4096
    - allow application to reserve, on a per-channel basis, how many
      octets from a logical pool of 65407 octets
    - allocate the remainder of the pool equally to those channels which
      don't have an explicit reservation
    - if the total reservations (excluding channel zero) do not equal
      65407, then all channels are scaled up or down equally

this allows "the right thing" to happen in most cases without any
application intervention. for example, in your application, your channel
would get about 59kB.
    
if an application needs to do something tricky, it can set relative or
absolute values.
    
what happens now, where beepcore-c allocates 4K to each channel is just
plain STUPID.
    
/mtr
    


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