dataflow?

[Raoul Duke]

the gpars folks make it sound like (as i read it) basically, "actors
are nice, but what you /really/ want is dataflow, because it hides all
sorts of extra cruft, it is a much nicer life for the app developer,"
and, "dataflow is implemented on top of actors," so i always wonder
about dataflow on top of any given actor toolkit cf. jactor.

[William la Forge]

When you have a firehose of events to process, nothing but dataflow will do. Which is why jactor supports buffered messages. And we have pipelines that support a million ACID transactions per second.

On the other hand, jactor works well at a finer grain than is normally recommended for actors. With regular actors I am almost inclined to agree that you might as well be using dataflow, but dataflow gets pretty tough to do as the granularity gets smaller.

--
You received this message because you are subscribed to the Google Groups "AgileWikiDevelopers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilewikidevelo...@googlegroups.com.
To post to this group, send email to agilewiki...@googlegroups.com.
Visit this group at http://groups.google.com/group/agilewikidevelopers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.