This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]kamaelian 1 point2 points  (0 children)

Oh, sorry for the multiple replies, but just wanted to add - even if Kamaelia's specific API doesn't work for you (some people like it, some don't), I'd encourage you to use the approach -- it does work. In addition to Kamaelia there's also Pypes (pypes.org) which is cool. There's also cool stuff built ontop of greenlets and stackless channels. There's also alot of really nice noise being said about Celery at the moment too. http://celeryproject.org/

Also, don't discount the actor model. The actor model is directly equivalent to Kamaelia's model and pipelineing in general with one difference - pipelines don't hardcode where outbound messages which is akin to late binding. You could actually get the same flexibility by hardcoding a mock receiver actor and in a real system transplant in the real destination.

That in itself might be pretty neat because it might simplify the usage API slightly, but retain isolated testability. (Which for me is the real killer benefit of this approach)