It is most suitable for parallel processing where you have lot of tasks that can be independently processed. If your tasks have shared states things are going to be more complicated. Fortunately this is changed with languages like Scala/Clojure. In both you have STM(Software transaction memory ) approach for writing application that share states.
Zlaja On Thu, Mar 3, 2011 at 7:46 PM, Jonathan Mitchem <jmitc...@gmail.com> wrote: > So, fundamentally, it's an architecture for dealing with "trivially > parallel" problems? Would that be an accurate summary? > > (Not to imply your problems are trivial.) > > -- > 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 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
