Server and multiple clients question
-
Hey guys, I want (just for fun) to create a poker (texas hold'em) server which allows up to 12 clients to connect and play a game of poker. I want to know what's the best approach to create a server - client application like this? I was thinking of creating a TCP Listener (server) and let clients (TcpClient) connect to the listener (server). Is this solution going to solve my puzzle or do I need to think in a different way? For your info : My goal is to get the poker server to work on my LAN. Thanks guys!
.: I love it when a plan comes together :. http://www.zonderpunt.nl
-
Hey guys, I want (just for fun) to create a poker (texas hold'em) server which allows up to 12 clients to connect and play a game of poker. I want to know what's the best approach to create a server - client application like this? I was thinking of creating a TCP Listener (server) and let clients (TcpClient) connect to the listener (server). Is this solution going to solve my puzzle or do I need to think in a different way? For your info : My goal is to get the poker server to work on my LAN. Thanks guys!
.: I love it when a plan comes together :. http://www.zonderpunt.nl
Hi, maybe you should check out .NET Remoting via TCP or HTTP-channel. It would be the easiest and fastest way to build up a distributed application like the one you're about to create.
modified on Tuesday, November 24, 2009 9:19 AM
-
Hi, maybe you should check out .NET Remoting via TCP or HTTP-channel. It would be the easiest and fastest way to build up a distributed application like the one you're about to create.
modified on Tuesday, November 24, 2009 9:19 AM
Erhm, I don't want the application or parts of the application to run distributed. I want one server application, and multiple client applications. The clients connect to the server. And for example, when a new client joins, the server sends a message to all clients that a new client joined and all clients seperately handle that message.
.: I love it when a plan comes together :. http://www.zonderpunt.nl
-
Erhm, I don't want the application or parts of the application to run distributed. I want one server application, and multiple client applications. The clients connect to the server. And for example, when a new client joins, the server sends a message to all clients that a new client joined and all clients seperately handle that message.
.: I love it when a plan comes together :. http://www.zonderpunt.nl
:) That is exactly what you can do with .NET Remoting. Check out the articles as regards this subject on the codeproject and you'll find what you're looking for. There're are a lot of examples there.