Could you send me (off list) a sample application that demonstrates the request-id problem you are referring to please.
As others have pointed out we already have a well defined log format. Adding more data sources to the TCP/IP connection you make to the server is on the TODO list, I have no time frame on when (or if) it will be completed. You should also use the hlds_apps list for discussions about tools, you can subscribe to it via http://list.valvesoftware.com/ - Alfred -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phraze Sent: Thursday, March 03, 2005 9:55 AM To: hlds@list.valvesoftware.com Subject: RE: [OT] [hlds] Re: Can anyone tell me how i can activate Stats -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Deadman Standing Sent: Thursday, March 03, 2005 12:47 PM To: hlds@list.valvesoftware.com 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. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phraze Sent: Thursday, March 03, 2005 8:32 AM To: hlds@list.valvesoftware.com Subject: RE: [OT] [hlds] Re: Can anyone tell me how i can activate Stats I think Valve has some opportunity to make improvements in statistics and remote administration features for their game servers without necessarily going all the way to implementing a fully persisted stats engine. Here are some thoughts: 1. Consider the use of XML for both log records AND rcon command/responses. While probably not an onerous development effort, this would make life easier in many development environments, across many platforms. Almost all current OOP environments have XML handling capabilities in their class libraries. 2. Consider devoting a bit more resource and attention to documenting and supporting these integration tools. 3. On the server side - consider choosing either udp datagram-based communications - or tcp stream-based for stats, queries and rcon commands. This would simplify the development of combined stats and game admin tools. 4. Clean up some of the things that are broken: the one that comes to mind is that the request-id on rcon commands is not reflected in the response message. Comments, Valve? Phraze _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
