Axel Dörfler wrote: > Adi Oanca <adioanca@xxxxxxxxxxxxx> wrote: > >>>>>Right, that's also a problem. >>>> >>>> That's still a problem. :-) >>> >>>You might have missed it (obviously), but the code doesn't suffer >>>from >>>this anymore after the rework. >>>Messages are flushed when a certain watermark is reached, and that >>>is >>>independent from the actual buffer size. >> >> Nah, I did a test to sustain my affirmation. >> I modified PortLink to show buffer size every time Attach is >>called. >>Then I added a 33K attachment to AS_WINDOW_HIDE (and read that >>message >>in ServerWindow of course). Also I put my window to do some >>drawing(window became visible after 2 sec). I forced redraws by >>moving >>another window above it, or move it outside the screen edge and back. >> >> The buffer remains at a value above 33K. > > > As I said, the buffer size has *nothing* to do with this anymore. > Have a look at LinkMsgSender::StartMessage() maybe you can believe me > then :-) I had a look yesterday, that's why I did that test in the first place. The buffer always grows at a max of 64K, it never shrinks back to 2K. Have another look, and this time maybe you should put you glasses. :-P I cannot believe you as I have my tests a a proof. ;-) bye, Adi.