"In my admin app, for example, I had to create two listening threads and ensure that I was managing mutex issues surrounding the simultaneous arrival of events on different "channels". Not impossible - but I was left wondering what design requirements lead Valve to the current approach. Almost like logging and rcon were developed by different people that didn't talk to each other - or they were developed at different time in the evolution of the product."
Or logging of game events and remote console (remote control of the server) are two distinctly different unrelated functions there by justifying status as separate communication entities. Separation allows rcon and logging to be implemented in the most efficient manor to achieve their different goals. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Deadman Standing Sent: Thursday, March 03, 2005 12:47 PM To: [email protected] Subject: RE: [OT] [hlds] Re: Can anyone tell me how i can activate Stats "Second I am unaware of any environment that can not easily handle the current data stream for either stats or rcon." I did not mean to imply that any environment might be challenged by implementing either datagram of stream sockets. In order to implement a application that covers all three of rcon commands, stats queries and remote logging, the developer currently has to use both - and this is a level of complexity that might be avoided, if there was a consistent, single stateful or stateless means of talking to the server. In my admin app, for example, I had to create two listening threads and ensure that I was managing mutex issues surrounding the simultaneous arrival of events on different "channels". Not impossible - but I was left wondering what design requirements lead Valve to the current approach. Almost like logging and rcon were developed by different people that didn't talk to each other - or they were developed at different time in the evolution of the product. As for the XML issue you are correct - lots of things you can do with regex, however, I like XML for more reasons that just parsing. In the end, I parsed the logs into XML once I got the stuff and that worked fine for me - for stuff like database integration and the SOAP/XML web service interfaces that I expose. However, here lurks a potential religious war - so I will defer on that one. We all use what works for each of us, in the end. I STILL would like the request-id reflected - as the rcon spec says it should be. Thanks for your post. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
