Comments on: Actors, concurrency and Kamaelia

By: itjob123

itjob123 — Wed, 02 Dec 2009 22:28:40 +0000

mini-axon is better . But now a days most of the related generators are there so what is the different between mini-axon and other generator

By: itjob123

itjob123 — Wed, 02 Dec 2009 16:28:40 +0000

mini-axon is better . But now a days most of the related generators are there so what is the different between mini-axon and other generator

By: Pipeline Construction Jobs

Pipeline Construction Jobs — Sat, 07 Feb 2009 11:05:56 +0000

I will make time though — my primary point was to almost say “getting to it busy omg”.

By: jnoller

jnoller — Wed, 29 Oct 2008 18:53:03 +0000

Axon may very well be a library - conceptually, I am beginning to see Kamaelia as you do - a "Kamaelia as a bucket of toys built using it", it being Axon.

I think what might help (conceptually) is a further decoupling of Axon from the bucket of toys - I think the roadmap for 2.0 you're talking about is great, it's the difference between Zope, and the various zc.* packages they have moved to.

I will make time though - my primary point was to almost say "getting to it busy omg".

As for the MPI - I started exploring various implementations of those as well, I should post my notes on those. The nice thing is is that with multiprocessing I can swap out the serialization mechanism(s) and use MPI freely under the hood.

By: Michael Sparks

Michael Sparks — Wed, 29 Oct 2008 18:39:32 +0000

Glad to hear it was useful :) Fully understand the time pressures - especially parental ones (have 2 small ones myself) :-) Also very much understand the motivation behind "I want to build one myself, to understand". Back at uni our lecturers very much liked quoting confucious at us "I hear and I forget. I see and I remember. I do and I understand". (this is very much the reason also behind the mini-axon tutorial :-)

For what it's worth, if you want any help/guidance through our code, just let me know. More than happy to help.

If you get a chance and would be willing, I'd be very curious to hear what you would view as a library approach rather than framework. I ask because, as noted, I think of Axon as a library & Kamaelia as a bucket of toys built using it, rather than as a framework. Also when Kamaelia hits 1.0.X I want to also move Axon to version 2.0.X. The core ideas that we want in Axon 2.0.X is the ability for people to cherry pick our stuff properly (Axon.Handle & Axon.STM are the beginnings of that) and so on. So any feedback (from yourself or anyone reading this) about how to make our system more usable in a pure a library fashion would be very useful.

But, if you don't have time/etc - no problem I've got similar pressures :) Also, I've been following up on the links you've been pointing people at, and will follow the links you've posted - these are much appreciated. (they're leading me down interesting avenues :) Also, I don't believe in one language, framework, or library to rule them all so any suggestions are welcome :)

Also, randomly, I agree about the need for an efficient interprocess messaging passing facility... It would be particularly useful for everyone...