Passing information from a service to a client via .NET Remoting
-
I have a .NET service that collects data from custom hardware. I want clients to log on to the service so I can do the Publisher-Listener pattern to publish updated data to the clients. Right now I have remoting objects that both sides use that are basically event containers. Server gets new data, server gets listener objects from listener collection, server transmits new data via the event to the client. Client observes event, unpacks and updates. Is this the best way to do this? The way it's laid out now seems hackish just to have classes that are nothing more than event containers. I also need additional scaffolding on both sides to observe the events and client request calls. The system is safety critical and the prototype application leaves a bad taste in my mouth. Does anyone have a different approach other than the event container, or should I get some mouthwash (or some bourbon) for the bad taste? Scott P
"Simplicity carried to the extreme becomes elegance."
-Jon Franklin