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

["Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>]

Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> * It would be nice to implement lazy copy on write for messages 
> (AFAIK Dano 
> does this). Especially in case of intra-app messaging we would be 
> able to 
> safe a lot of operations, for often messages are created, sent and 
> then 
> just deleted by the sender. If {Send,Post}Message() would just add a 
> lazy 
> copy to the target looper, we had a zero-copy message delivery in 
> this case.
> 
> * Dano uses shared memory to send big messages. This does, of course, 
> work 
> best, if the message data are already stored in a flat single buffer. 
> But I 
> suppose your three buffer design isn't that bad either for the task, 
> since 
> for a big message we could send the message header and the field 
> headers 
> through the port and use shared memory for the item data.

What about those two items, Michael - do you feel like implementing 
them? :-)
At least zero copy messages for intra application usage sounds like a *
very* good idea to me.

Bye,
   Axel.