Re: Dynamic dispatch again

[tmoran@acm.org]

>example, a task that would receive each fragment of the message until
>all fragments had arrived, concatenate them, and present them as if they
>arrived in one chunk, or a task that would accept a message, blocking
>the caller until it had actually been put on the wire, etc. I can
  I'm not sure I understand what you are trying to do.  It sounds like
you want a bunch of low level tasks running various message channels.
Sort of like Ada.Text_IO, Socket_IO, Serial_IO, that kind of thing.
They handle buffering, timing, etc on their respective devices.  Then
the programmer is presented with a single interface where overloading
determines what's called, eg Put_Line(F,...) calls Text_IO if F is an
Ada.Text_IO.File_Type, Socket_IO if it's a Socket_IO.File_Type, etc.
In that scenario the programmer never codes a "select" or a queue,
but calls a routines from your library which handle that stuff.  Is
this closer to what you are driving at?  Ignoring implementation,
can you write down the specifications for the abstraction you want
your users to see.