intertwingly

A brief sketch on my thoughts on the subject: a process should manage its own state with transfers of state between processes between processes being done through representations of resources.

Within a process, things work best when everything uses a common runtime, so one answer would be to get Python on the CLR. The current state of this effort is at best incomplete. The approach taken by ActiveState was experimental, and other approaches should be explored. I have ideas, but it is a big job so it is one that I am unlikely to have time to work on them. The other answer is to get Aggie functionallity in Python. The latter would be a much smaller job.

If we are looking at multiple processes, the next question that needs to be resolved is the selection of the representation that is to be exchanged. In this case, I would answer RSS, and architecturally I would end up with a solution like blagg. In my case, the server portion I would like to deploy on Linux, so if it were to be C# I would want to use something like Mono.