.NET Framework
|
|
 |
|
Last November, I was trying to do a multi client program for a Question And Answer game, the game is like this:
1. The judge (ok, this is a real people) ask a question, and then on his Master Terminal (computer-server), he click "start answer"
2. Then the participants (real people) on their own computer, can click "answer", if they want to answer that question.
3. Master terminal will show all intended participants, and the fastest one will "Flash" on both Master terminal screen and the Client screen.
4. Master terminal can also set the score and the score will be shown on (participants)client screens.
I tried to implement this with remoting at that time. But I found a couple of problems when I am implementing that. First, what I have in my mind is for remoting, the application code should not realize that they are calling remote objects or local objects, this should be done by the transparent proxy objects. It is definitely achievable without any problem when creating remote objects, calling methods of that particular objects, but when it comes to events and delegates, it is a different story. I have to make the client expose to another port to listen the event fired from remote objects, and moreover, another dummy object have to be declared in-between the remote object and the client application. (see the method shown here: http://www.codeproject.com/KB/IP/RemotingEvent.aspx?msg=2821954[^])
The use of intermediate object totally breaks the beauty of transparent proxy, and make the code became messy.
So, my question here is, in doing such project, am I using the wrong technology? Should I use WCF or the old school TCP Port listener?
modified on Wednesday, February 18, 2009 7:41 PM
|
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Rant 
Admin
Submit an article or tip
Post your Blog
