Some time ago, Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote: > > They shouldn't matter much, that's right - but of course, > > everything > > adds up, so saving some copies could also save some time :-) > > But sending additional data should be always cheaper than managing > > another structure on the client-side. > > But I would probably try to use shared memory for the IPC - as long > > as > > the kernel doesn't provide that feature built-in. We could do the > > same > > for big BMessages as well. > > Of course, we could also just add this feature to the kernel as > > well - > > but it should be controllable by the applications involved (so a > > user- > > space implementation would also make sense [if it would be in a > > library > > usable by everyone]). > Sounds nice. In any case, care must be taken. Shared memory also > means, > that the application has full access; so, if running amok, it may > overwrite important data of other apps's (or in worst case, the > kernel's) > ports. Shared memory doesn't have to be writeable for everybody, though :-) Adios... Axel.