Funny Architecture:

While trying to land a client, working on our technology and fidgeting with Amber (BTW is like a breath of .Net in a see of Java :-} I ran into the following paragraph (page 15 Pallmann's book):

"Instancing behavior determines how many instances of a service are created for clients (for example, one per client session)..."

which I find kind of funny. What about the object state? Say that service "A" gives access to or sells lottery tickets. How would one instance know which numbers are available?

Is Indigo going to force static members?

Or it is just intended to stateless classes? (my example is an over-simplification but before we know it stateful classes will be involved)

Anyways, I think it is their problem. I am just trying to avoid them:-}