OK, sounds good Raymond. Can we now discuss what we should do about the remote support for the SCA binding. At the moment we are only able to support a single distributed binding provider and we construct independent distributed SCA binding provider implementations, for example, binding-sca-runtime-rmi, to fill this role.
A little while back we talked about relaxing this restriction so that bindings could advertise their availability to play the role as the distributed SCA binding provider. The object of this would be to allow the runtime to be able to choose what sort of distributed protocol to use based on the environment and policy, for example, if reliable messaging is required maybe JMS would be chosen over RMI, etc. Maybe before we try and make technical decisions we could try and come up with a set of specific scenarios that we can develop against. If the list is empty I guess we don't have anything to do. Regards Simon
