Now THAT"s what I'm talking about. Augment such a solution with interruptible & resumable data producers, and I'd have everything I need.
Regards, John A. De Goes Twitter: @jdegoes LinkedIn: http://linkedin.com/in/jdegoes On Mar 27, 2011, at 10:54 PM, wren ng thornton wrote: > In an ideal framework the producers, transformers, and consumers of stream > data would have a type parameter indicating the up-stream communication they > support or require (in addition to the type parameters for stream type, > result type, and side-effect type). That way clients can just define an ADT > for their communication protocol, and be done with it. There may still be > issues with the Expression Problem, but at least those are pushed out of the > stream processing framework itself which really shouldn't care about the > types of communication used. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
