Folks, I'm starting work on a "HostContext" that would allow a single client to actually hit multple servers for method invocations. The following scenarios would be possible:
1) Client opens a connection with a random* server and continues to route methods calls to that server 2) All method calls would hit a random* server (no stickiness) * Secondly when we say random, there are likely to be other implementations that are useful: a) Some sort of querying load capability solution. One server is asked which of others in its fedaration should be hit with requests. b) Simple rotating load balancer, first connection uses server0, next server1 etc. What is would be considered the most important to do? Would there be anything else that would be useful at this stage? Regards, - Paul H -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
