NGWS SDK Documentation  

This is preliminary documentation and subject to change.
To comment on this topic, please send us email at ngwssdk@microsoft.com. Thanks!

Remoting-By-Ref

In some Remoting situations, certain objects may be marked as Remoted-by-ref. In this case, the original object remains where it is. On the remote node, we establish a transparent proxy – it behaves, for all the world, like the real object. However, any accesses of its fields are passed back to the original object.

Serialization itself does not ‘know’ how to encode information that enables Remoting to create that proxy object. This is accomplished through the Remoting service using a Surrogate for that Remote-by-ref object.

Note that in a graph of objects, some may be specified as Remote-by-val whilst others are specified as Remote-by-ref. As soon as Serialization encounters a Remote-by-ref object, it does not walk any subtree that object may have.