Re: two way comminucation in Remoting
- From: Mehdi <vioccc@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 5 May 2006 09:58:08 +0100
On Thu, 4 May 2006 17:30:01 -0700, BJ Honney Cut wrote:
Is it possible to enable a two way communication via remoting.
i.e. from the client side, i execute a method on a server object (singleton)
via remoting and also pass a reference of the client object (inherited from
MarshalByRefObject) which will be maintained on the server remote object.
Thus, at the end of the call, the reference will be maintained on the server
remote object.
Then at a later time, from the server remote object, can i call a method on
this client object (to which a reference is available)???
Yes. The interface of the client's MBR must of course be present in the
Known Layer (the DLL shared by both the client and the server application).
Note that since the .NET Remoting built-in channels are not
bi-directionnal, when the server calls back a client, it needs to open a
connection to the client's machine which might not be possible if the
client is behind a NAT proxy or a firewall bloking the neededb port. If the
client is not behind a NAT proxy and you have control over the client's
firewall, then you should register a server channel on the client side
specifying a port which is going to be used by the server application to
connect back to the client. Then open this port in the firewall. If that's
not possible, you'll need a bi-directionnal channel such as those provided
by Genuine Channels (<http://genuinechannels.com/>).
.
- Prev by Date: Re: Stop server thread from client
- Next by Date: Re: Stop server thread from client
- Previous by thread: System.IO.FileLoadException on a previously working project.
- Next by thread: hooks to ORPC?
- Index(es):
Relevant Pages
|
Loading
