[haiku-appserver] Re: communication
- From: Adi Oanca <adioanca@xxxxxxxxxxxxx>
- To: haiku-appserver@xxxxxxxxxxxxx
- Date: Fri, 10 Jun 2005 08:54:49 +0300
Axel Dörfler wrote:
> Adi Oanca <adioanca@xxxxxxxxxxxxx> wrote:
>
>>>> Yup, in concept. I wonder what happens if I want to transfer a
>>>>10K region? That region will be transfered to app_server, but the
>>>>buffer will remain at 10K ! That's a _bad_ thing as the buffer is
>>>>too big
>>>>for caching drawing commands and the GUI will be less responsive.
>>>>It's enough that the initial buffer has 2K (R5's one is 1K), but
>>>>10K is
>>>>already too much!
>>>
>>>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.
bye,
Adi.
- Follow-Ups:
- [haiku-appserver] Re: communication
- From: Axel Dörfler
- References:
- [haiku-appserver] Re: communication
- From: Axel Dörfler
Other related posts:
- » [haiku-appserver] communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- » [haiku-appserver] Re: communication
- [haiku-appserver] Re: communication
- From: Axel Dörfler
- [haiku-appserver] Re: communication
- From: Axel Dörfler