It might be worth your while to look at netwire or auto, which both use arrows to model networks.

Ben

On Tue, 31 Mar 2015 at 06:35 martin <martin.drautzburg@web.de> wrote:
Hello all,

little do I know about arrows, but the "stream processor" metaphor suggests, that they can be used to simulate a network
of things, services or data. Is this correct?

I came across the following thought: When I simulate a billard game with a DES, I would compute collisions of balls with
each other and with the banks, creatign a set of events, of which only the earliest will be considered to compute the
next state. This is pure DES and does not seem to be a good candidate for arrows. In this case I'd be more interested in
composing collision detectors than in stream processing.

OTOH, when I move parcels around and process then in various stages, then a "stream processor" would make perfect sense
to me. In that case, would I abandon the DES paradigm entirely (including the notion of an event queue) and just model
the network and let it run?

_______________________________________________
Beginners mailing list
Beginners@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/beginners