Hi,
I'm writing another multimedia RTOS and looking through the code I've written that *used* other such beasts in the past (wise move, eh? :> ).
It seems like moving zero-copy semantics *formally* into the RTOS's contract should help improve application robustness -- instead of relying on ad-hoc implementations by the developer.
Of course, this makes it a bit more cumbersome to pass small objects around :< I suspect the interface could be bastardized to support
union { void *, }
thought that seems a real kludge.
But, I really can't see many places (in *this* application) where such small objects would need to be handled (?).
What sorts of experience have other folks had in using formal IPC channels with "small objects"? Is it worth "coloring" the channels to support two different types of interface?
Thx,
--don