Amber Host:

After several interactions over email with the other Amber developers and managing to get some time off my transatlantic move chores, I am working on the host.

Some of the features are so far:

*) Per service AppDomain setup and security evidence: each type will have the opportunity of passing to Amber the setup and security evidence that has outside it.

*) Leases: it will be up to the service provider to tell the host if it wants to remain inside the host. This way hosts do not suffer from "dead" services.

*) Public/Private exception handling: as in any other piece of software a service user should expect a method to throw exceptions. The service provider may want to keep some exceptions outside the public's eyes. Public/Private exception handling will help in that regard.

*) Multithreaded services: say that user "a" is accessing service "b", method "c" and user"d" is accessing service "b", method "e". If the costs of thread bookkeeping are not excessive, the host could expose both methods in different threads (well, this is a big ?)

Red Tape Follies:

1) What do you do when official agency "A" tells you to call official agency "B" because they are to handle the issue. You call official agency "B", but official agency "B" tells you to call official agency "A"?

2) Official agency "C" gives you a form that may or may not work with official agency "D" but if it does not work please update them to make the form more usable but not official!?!?