Yes, you can use this pattern to define a mini-interpreter for a stream of events or commands, where each event is represented as a data structure.
For example, I've used this pattern to write little scripts, a a collection of maps, for driving an integration test. –S On Monday, May 25, 2015 at 10:57:22 PM UTC+1, piastkrakow wrote: > > Stuart Sierra, > > Thank you for the response. I won't take that talk as encyclopedic. > The 'chain-consequences' function is very interesting, though it is > unfamiliar to me. I am still learning about Clojure. > > You mention that the State/Event pattern is a common one. If you were > talking about architectures, I would say your description reminds me of > Kafka (events are data structures, replaying events can replay the whole > history of state in the app, etc) but I am curious where you feel this > pattern shows up as a design pattern? I assume you mean to broadly define > this to include those situations where we might use pure functions in loop > or reduce to iterate over a "message" where the "message" is some data > structure, perhaps a JSON document, or some other kind of seq generated by > an event? > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
