wolfc wrote:

 

Serialization of a remote proxy can happen within any context. It could be because the proxy was dropped in an HttpSession, which can get serialized for any reason or it was injected into a far-away SFSB that's passivated.

I think it's safe to assume that the context is generally always available from a yet-to-be-serialized proxy, one way or another.  I will update the document to this effect.

wolfc wrote:

 

I'm also missing bits for security and transaction propagation.

It's implied (vaguely) in the discussion of attachments.  I'll elaborate that section a bit.

Updated: done!

I've made some major updates to this doc based on the past couple days' discussion.  I think I've addressed all the serialization & proxy cases.  I still haven't covered configuration & bootstrapping for client environments but it's getting closer.  Also, HA is still unspecified other than a few vague references to letting Dispatchers and Forwarders do whatever they want.

One major change is that the concept of "Remote Invoker Context" has been split up into client and server components.  Please let me know what you think.