Ken Kolda
9/21/2004 6:05:00 PM
Actually, since this is a SAO, the client app will actually create the proxy
for the object itself -- it does not get returned by the server (that's what
happens for CAOs). So, having additional properties/methods on the
WidgetManager will have no affect on the performance of obtaining a remoting
proxy.
As for viewing the proxy that's created, that's not really possible for a
SAO (as far as I know). For a CAO it's possible to serialize the proxy's
ObjRef, but for SAO there is no ObjRef (you can see that yourself by calling
RemotingServices.GetObjRefForProxy() on the SAO's proxy -- it will return
null).
Ken
"Joshua Belden" <JoshuaBelden@discussions.microsoft.com> wrote in message
news:80762A02-664A-449A-9B67-EAFA89A4519C@microsoft.com...
> I have an object, WidgetManager, on the server that exposes CreateWidget()
to
> return Widgets back to the client. I've created a well-known Interface
> IWidgetManager that defines CreateWidget() to provide some isolation
between
> the client and server.
>
> However, WidgetManager is actually used for some additional related
> operations and is exposing public methods, that are not defined in
> IWidgetManager.
>
> When clients get a proxy to the IWidgetManager object, I know that they
will
> not get the methods defined in the main WidgetManager class, but will
> additional data be transported accross the pipe because of the additional
> methods exposed? Am I correct in assuming that the proxy created will only
> contain methods exposed in IWidgetManager.
>
> Additionally, how can I examine the actual proxy that is created?
>