Remoting and events
I'm completely disappointed of .NET Remoting. I'm developing an application which requires messages to be sent from a server computer to clients connected to it.
Apparently (correct me if I'm wrong) there are two ways to do that:
- TCPChannels and direct tcp communication
- .NET Remoting
Since I find TCPChannels to be very low level procedure, I want to use .NET Remoting. However I've lost the whole day searching for code on how to implement events over remoting. I haven't found very few incomplete examples for .NET 1.1 and VS2003 and none for .NET Framework 2 and VS2005.
I finally came to this forum to find out that .NET Remoting's future is questionnable!!!
Please give me some words of comfort!
Dimitris
[776 byte] By [
papadi] at [2008-1-21]
Hi Vikram. Thanx for helping me out!
First sample seems clear enough! I hope nothing changed in framework 2. It seems that this sample does not use events back common procedures to send messages back to the clients!
All samples I found so far (including the 3rd article you suggest) were using common events and GetInvokationList to get the subscribers. I never made that to work!
...on second thought... it doesn't seem that clear! For instance, when removing a client, it's not deleted fromt he subscribers collection. So when another one is being added an exception occcurs, so further checks should be made.
It seems that remoting events are to hard to implement and require low level stuff that should be hidden from the programmer. I'm going to use TCPClient for the moment!
