Axum Implementation

Hi,

After reading the Language Spec and Programmer's Guide, I remember a note stating that the user had 500,000 waiting agents.  This sounds like the micro-thread idea behind Stackless Python - is the implementation along the same lines?

I noticed in one of my tests that having an agent block to wait for a receive completely removes any (noticable) processing in that agent, where as, say, setting a polling mechanism in the agent causes the agent to continue execution (obviously).  Is there an under-the-hood scheduler/manager for agents to share one thread ala Stackless?

I'm waiting for the day when some bright spark implements an ASP.NET server in this akin to Yaws (Erlang web server).

One concept I haven't yet had time to get to grips with in the Interaction Point objects (OrderedInteractionPoint).  Where do they come into play?  I made a simple app where two agents constantly message each other with an incremented number and print it (co-routine), purely by using send and receive statements.

Sorry for the vague questions.

Adam