Re: Unnecessary Frame Fragmentation using beepcore-c?

Any idea what the default window size is, and what a good window size 
would be in order to facilitate the sending of full 4K frames?

In the receiving profile, it appears to be defaulting to 4K.  Should it be 
4K plus some extra space for some structure that must be passed?

I've tried bpc_set_channel_window(pi->channel, 10000L) in the receiving
profile, which seems to work, but it still fragments just as badly.

Perhaps I need to also set it in the sending profile?  Or perhaps Darren
New is right that I am pushing the lower layers too hard and making them
send partial frames -- in which case I'm not sure what to do.

I've already modified the application to deal with partial frames, so it 
is really performance I am concerned about more than convenience.

DCN

On Fri, 12 Sep 2003, William J. Mills wrote:
> bpc_set_channel_window() can be called within the context of a profile on 
> it's channel object.
> 
> That's in bpc_wrapper.c in thew rapper directory.
> 
> -bill

-------------------------------------------------------
-- David C. Niemi           Adeptech Systems, Inc.   --
-- Reston, Virginia, USA    http://www.adeptech.com/ --
-------------------------------------------------------




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