real-time constrains for tunes migration

[Mark Baily]

One of the problems involved in real-time operations such as music or graphics
is specification of those operations which have constraints in terms of how
long operations are allowed to take. In distributed programming the encoding of
any communications (serialization) may be done on a continuum of flexbility vs
speed. As is typically done, hand-crafting purpose-built protocol examples are
"Open Sound Control", "MIDI", "Chromium" (for streaming opengl primitives) or
CORBA real-time.

But hand-crafting such protocols results in a lack of a continuum for real-time
operations, meaning lack of expressivity for specifiying small, medium and
large time values and in between, for operations, let alone programatically
determining these time values.

Instead, encodings/protocols can be automatically generated by a program, based
on a specification of speed required for each communication.  How does this fit
in with the Tunes migration project.