Monday, July 17, 2006

Joined nodes

Scenario, based on the high level concept of PI calculus:

Nodes are joined by Channels. I contrive my Node to send my Message (a request message, requiring a response) to the target Node via one of it's public Channels. It will reply with some response Message.

Now, if I know what I want, but don't know or care where it's from, I will get my Node to go find a service Node that can answer me.

I can do this as a higher level layer over something like Java, TCP/IP, XML, etc and get something out quicker.

Friday, July 14, 2006

Objects, Types, Messages, Channels and Nodes

The thinking is like this:
Object - basic nugget of structure
Type - the introspection into an object (meta-object perhaps) says what Messages an Object recognises.
Message - a 'prod' to an object
Channel - a route for a message to get to an object
Node - martialling for messages and channels, container of objects, security

As a base for a programming language, there's too much stuff here for my liking! Also, what comes first? What's the basis of the language? Objects are the popular choice of course, but you need the other stuff.. I guess we haven't even started with any basic Types yet either, like String, Numbers, etc..

hmm..