Event counters

[GoogleCodeExporter]

This will be similar to the World Stats, especially the counters in World 
Stats. But the idea will be to make it even more generalized. Each event would 
have a single source (e.g. user, character template, item template), a single 
counter identifier, and a single value for the counter. This differs from World 
Stats who's counters actually keep more details. While the World Stats kill 
counter keeps track of who they killed, the Event Counter equivalent would keep 
track of only that they killed.

This would provide a much lower overhead alternate to World Stats, namely for 
more frequent operations. It'd be far more simple since only one table (with 3 
columns) is needed for each object type. Performance will be far greater since 
caching can easily be done instead of querying every single operation. If 
possible, could even utilize batched queries when caching since they'd all be 
on different rows in the same table. Finally, there'd be far less storage 
overhead since the max rows any object could even have is equal to the number 
of event counters they have.

It won't be part of World Stats due to the design difference. World Stats 
resides mostly all in the actual DemoGame since its mostly all in the queries, 
there are a lot of queries for it.

Original issue reported on code.google.com by Spodiii on 24 Nov 2010 at 8:22

[GoogleCodeExporter]

Original comment by Spodiii on 9 Dec 2010 at 5:38

• Changed state: Started

[GoogleCodeExporter]

This issue was closed by revision r4395.

Original comment by Spodiii on 9 Dec 2010 at 10:30

• Changed state: Fixed