Re: [Beepcore-c-users] Unnecessary Frame Fragmentation using beepcore-c?

[Darren N. <dn...@sa...>]

William J. Mills wrote:
> bpc_set_window_size will return the recieve windows size, but
> not the peer's.  It returns the plocal size with an arg of -1
> and takes no action.  Perhaps we should add a -2 to get the remote
> size....

I'd suggest checking the documentation to see what I called it. I 
actually did think it through, and generally I think you want to be able 
to tell both how big the window is Right Now, and how big the window has 
been in recent times. I.e., you want to be able to get an idea of what 
the argument to the peer's bpc_set_window_size is, altho that's 
naturally harder than just looking at what we know right now.

-- 
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.