Home/ Questions/Q 4343574
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T11:46:23+00:00

I am attempting to send player information from my Game to my network client

  • 0

I am attempting to send player information from my Game to my network client to then be sent off to the server.

Currently the ClientNetwork -> ClientGame relationship is held with XML files. They read/write back and forth at very high speeds. If you use just one XML file for this trade, one will “hog” the file at times, making a kind of lag when one cannot read because the other is viciously writing and rewriting.

To fix this I have 2 of each of my XML files. If it cannot read one, it will read the other. In theory they should be using both of them, since it’d be a tradeoff from one to another. Not working up to par.

But my main problem is just the usage in general of XML is very sloppy, dozens of try-catch statements to make sure they’re all happy (and my personal favorite, try catches within try catches — WE HAVE TO GO DEEPER)

I am just curious of if there is a better way to be doing this. I need a static point of variables that can be accessed by both client side programs. I’m afraid someone is going to say databases…

I’d like to state for anyone who is looking into this as well and stumbled across this page that Shared Memory is awesome. Though I have to convert all strings to characters and then to bytes and read them one by one, in the whole it’s ALOT better than dealing with things that cannot read/write the same file at the same time. If you wish to further understand it rather than just use it, go to this link, it explains a lot of the messaging varieties and how to use them.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Yes there is!

    The term you are looking for is interprocess communication – communication between two processes on the same machine.

    There are various methods which allow two processes on the same machine to communicate with each other, including:

    • Named pipes
    • Shared memory
    • Sockets
    • HTTP

    Fortunately C# applications can simply use the WCF framework to perform IPC (interprocess communication) using one of the above, and let the WCF framework take care of the difficult bits! Here are a couple of guides to get you started (there are many more):

    Also, one of the neat things about WCF is that you can also use it to communicate between different machines simply by changing the “Transport” (i.e. the communication method) to one which works over a network, (e.g. HTTP).

    If you are targetting .Net 2.0 then you should look into either .Net remoting or web services instead.

    • 0