Re: Events in .Net Remoting

Thanks for the reply. I think I have got the thing working...but with a
different workarround.

I was already doing the same as suggested by you i.e. opening up a new
channel for the callback to be sent on the client and also specifying
that the client will allow callbacks to come on any open port (port:0).

My architecture was such:

(Client) <-- .Net Remoting --> (Server)<---->(RemoteObject.dll)

to send an event, the server needs to know what is the type of event
handler at the clients end. This might entail giving a reference of the
client exe to the server, or worse copying the client where the server
stays. To circumvent this, the article that I was using had suggested
to have the the event handler at the client's end as a derived from
another remotable class (which is itself derived from
MarshalByRefObject) that has a virtual funtion, whose signature and
return type matches that of the delegate set up for the event handling.

This virtual funtion is then implemented at the client side to do the
event handling.

The deal here was that the base class (from which the event handler
derives) must also be explicitly visible to the RemotableObject. Though
it anyway lives in the RemoteObject.dll, it should be made visible by
including the header file of that class.

After I did that...it started working fine.

I will post more questions as they come up. Thanks for the reply
again...

.

Relevant Pages

  • Re: How to do a post back when user press enter.
    ... It is hosted on a web server, ... the client browser, which is designed to read and interpret HTML. ... UI, via the event handler. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Newbie Question
    ... A WebForm ALWAYS posts back to itself. ... with client-side events handled on the server side. ... > an event on the client occurs that has a server-side event handler, ... > interface being returned to the client. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How to do a post back when user press enter.
    ... > requested by a client browser, ... > by an ISAPI (Internet Server Application Programming Interface) ... > and interpret HTML. ... > to its process and UI, via the event handler. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: More client server problems
    ... > call a read from the client side that would block waiting for the server ... Transferring octet streams between TCP clients and servers? ... Why can you not exit the event handler & get ...
    (borland.public.delphi.language.objectpascal)
  • Re: Newbie Question
    ... I know it has "ASP" in the name, ... with client-side events handled on the server side. ... an event on the client occurs that has a server-side event handler, ... interface being returned to the client. ...
    (microsoft.public.dotnet.framework.aspnet)