[haiku-appserver] Re: Shared Memory Allocation

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Sat, 04 Sep 2004 18:26:15 +0200 CEST

"DarkWyrm" <bpmagic@xxxxxxxxxxxxxxx> wrote:
> I just changed our pool allocator from a bunch of C code (and ugly at 
> that) to a class so we can have multiple pool managers in the same 
> application without conflicts. We are going the same route as R5 and 
> setting up a general application area. We will eventually be moving 
> BBitmap storage to this shared area to prevent a bad app from 
> overwriting BBitmap data in another app, but one question still 
> remains: how should we send over a large object? Should we create a 
> new 
> area, dump it there, and tell the server to look there, or should the 
> client ask the app_server for a memory chunk to write to, write to 
> it, 
> and then send the message? I'm kinda concerned about overhead and I 
> wondered what the rest of you gentlemen thought.

You can create the area in the client, send its area_id to the server, 
clone it there, and delete the area in the client, if you don't need to 
access it anymore from there.
Does that fit to what you need?


Other related posts: