[openbeos] Re: A new BMessage implementation (Message4)

On Thu, 10 Nov 2005, Axel [iso-8859-15] Dörfler wrote: 
mmlr@xxxxxxxx wrote:

At least zero copy messages for intra application usage
sounds like a *very* good idea to me.

Yeah, copy on write and such. I suppose the design is very well
compatible with this concept, so it should be at least doable if not
easy.

Shouldn't that merely be a matter of maintaining a reference count and make a copy of the buffers when a write operation is going to be performed?

Also the shared memory for large messages is certainly possible. I'd
place the data and the fields buffer there and send the header
through
the port.

If possible, I would rather start allocating the data buffer in an area once the data hit a certain size. And I would think one can send both header and fields buffer through the port, which saves the hassle of copying the former -- it probably won't be that big anyway, even if there are a lot of data.

The same copy on write principle can be applied there. 

Between applications?

[...]

CU, Ingo

Other related posts: