A 'stream/callback interface' can be modelled as a pair of files, one of
which is a source of data and one a sink, or as a single file which you
can read() responses from as you write() stuff to it. Anything you can do
with a TCP/IP socket you can do with a suitably backed file, and we know
very well that you can define protocols over network sockets :)
Posted Sep 23, 2008 6:35 UTC (Tue) by lysse (guest, #3190)
[Link]
That just shows that the two models are equivalent in expressive power, like inheritance and delegation. If we couldn't synthesise one from the other, JACK couldn't exist - but it'd still be nicest of all to have both available at the lowest level :)