> With PortLink... all things are beautiful, every command is cached, and > every command is *complete* when it reaches the app_server. And that's the problem. Since Portlink will also be used to implement BScreen::WaitForRetrace(), do you think that the caching is a good thing ? > - when our message is bigger than 1024 bytes, we should allocate a new > _BPage_ add it to the list and write data into it just like you > said(directly). > > Then when Flush(), we'll alocate a new buffer witch is equal with our > message size, copy all the data from _BPage_s into it and sent it to > app_server. > Then we should just use BMallocIO, as Ingo said, since it does exactly what you said.