On Dec 8, 2010, at 821AM, Gregg Wonderly wrote: > > The current situation with how lookup returns an unmarshalled object limits a > client choice to much earlier "binding". That is, instead of being able to > look at multiple service matches and say "this one is not for me", it needs > to, instead, be connected with the service deployments via an Entry which > might indicate what "platform" the server can support. This is not always a > problem and I don't want to undervalue how Entry can be used to do this. > > Deferred unmarshalling in lookup could provide some more powerful decision > opportunities for the client by allowing it to better manage when that occurs. >
I agree, deferred marshaling and using lookup attributes can certainly aid in how this can be accomplished.
