Stumbled across this via slashdot yesterday:
http://msdn.microsoft.com/en-us/devlabs/dd795202.aspx
Looks like Microsoft trying out concurrent programming with loosely
coupled components/agents that communicate using asynchronous message
passing.
It seems to be implemented as (yet another) language for .NET ...
which is rather nice in its own way as that means it can presumably
use the full library/framework facilities in the .NET environment ...
and perhaps might run on Mono too.
There's a PDF overview/intro to the language here:
http://download.microsoft.com/download/B/D/5/BD51FFB2-C777-43B0-AC24-BDE3C88E231F/Axum%20Programmers%20Guide.pdf
At first glance, I quite like their approach to defining the
'contract' between components - by decoupling the definition of inputs
and outputs from the components. It seems the approach is to declare a
separate 'channel' (ie. a collection of typed, directed postboxes).
Rather like declaring the arguments to a method/function call. One
component is deemed to 'provide' the service declared by the channel,
and others consume. I reckon this is pretty analogous to declaring an
interface and having a separate implementation.
Matt
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"kamaelia" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/kamaelia?hl=en
-~----------~----~----~----~------~----~------~--~---
