Implementing server capabilities

[koraktor]

This issue was reported by koraktor, Mar 14, 2009 on Google Code

Steam Condenser's architecture was designed with the idea, that it should be easily extensible. So here's a quick idea I had: It's no big problem to make Steam Condenser not only a client library sending queries and getting results, but also make it a server library for listening for queries and sending results.

This may have several uses:

• Give other developers the chance to support a well known and widely used protocol in their game.
• Proxies: Steam Condenser could be used to proxy requests to e.g. LAN servers. I'm not sure if this may be of any use to server admins.
• Testing: The server library could be used to test the client library and vice versa. Not for the protocol itself as this should be coded right for both, but testing for others errors would work without the need for a running game server.

Just some ideas.

[koraktor]

This comment was posted by ccondrup, Mar 17, 2009, on Google Code

Going out on a limb here, hope I understood correctly and am not way off; Would such a server side library be able to incorporate any kind of server benchmarking?

• I for one would very much like to see a form of GoldSrc server benchmarking. I would like to see specifically how well this server type performs on a Pentium4 based server, as opposed to on a Core2 or similar multi-core setup. (Given that this old engine isn't specifically built to take advantage of multi-core/-threading, the question isn't that straight forward)

[koraktor]

This comment was posted by koraktor, Mar 19, 2009, on Google Code

No, I think you misunderstood. This "server side library" would do nothing else than send responses to incoming queries. I don't think this would be of any use for benchmarking.

[koraktor]

I don't think this is really needed. There won't be a server-side implementation until anyone really needs it.