Home/ Questions/Q 249149
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T21:24:09+00:00

I’m working on a 4-player network game in WPF and learning WCF in the

  • 0

I’m working on a 4-player network game in WPF and learning WCF in the process. So far, to handle the network communication, I’ve followed the advice from the YeahTrivia game on Coding4Fun game: I use a dualHttpBinding, and have use a CallbackContract interface to send back messages to clients. It works pretty well.

However, my service is getting very large. It has methods/callbacks to handle the game itself, but also the chat system, the login/registration process, the matchmaking, the roster/player info, etc. Both the server and client are becoming hard to maintain because everything is tied into a single interface. On the client for example, I have to redirect the callbacks to either the game page, the lobby page, etc, and I find that very tedious. I’d prefer being able to handle the game callbacks on the game page, the chat callbacks on the chat window, etc.

So what’s the best way to handle that? I’ve thought of many things, but not sure which is best: splitting the service into multiple ones, having multiple “endpoints” on my service, or is there other tricks to implement a service partially where appropriate?

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You should have multiple components, each of which should be limited to one responsibility – not necessarily one method, but handling the state for one of the objects you’re dealing with. When you have everything all in one service then your service is incredibly coupled to itself. Optimally, each component should be as independent as possible.

    I’d say start with splitting it up where it makes sense and things should be MUCH more manageable.

    • 0