Bug 812642 tracks removing data pipe support from the EDK and building it in the public C++ system library instead.

Recent discussions around data pipes have given rise to additional considerations about how we might extend or supplement the existing data pipe API with new things once that move is done.

Of some minor interest to me are:

 - introducing a type of data channel that supports framed messages
   rather than fixed element sizes - presumably only supporting full
   frame writes and reads and not doing best-effort partial delivery.
   in other words, a pseudo-message-pipe in shared memory.

 - introducing a data channel using a lock-free ring buffer and no
   message pipe for signaling. I have no idea how this could possibly
   work without some kind of cross-process signaling mechanism