B
Bob
Let's say I want a program running on one computer to
interact in real time with a program running on another
computer.
With Remoting, I can use a client object to create or
connect to a server object and access its methods. But
the server object only "responds when asked". I don't see
how it could "raise an event" to the client object,
thereby facilitating a "two-way" conversation where
either object could initiate a process on the other.
Example: You are the user of a "log sawing client
program" which uses remoting to connect to and control
a "log sawing" device. You have buttons to start the cut,
control the width and speed of the cut etc. But what if
the saw gets jammed? You only find out that the saw got
jammed when you send a new command regarding the cutting
process.
I need the saw to raise an event that it's in trouble!
interact in real time with a program running on another
computer.
With Remoting, I can use a client object to create or
connect to a server object and access its methods. But
the server object only "responds when asked". I don't see
how it could "raise an event" to the client object,
thereby facilitating a "two-way" conversation where
either object could initiate a process on the other.
Example: You are the user of a "log sawing client
program" which uses remoting to connect to and control
a "log sawing" device. You have buttons to start the cut,
control the width and speed of the cut etc. But what if
the saw gets jammed? You only find out that the saw got
jammed when you send a new command regarding the cutting
process.
I need the saw to raise an event that it's in trouble!