Quote:
Originally Posted by Akkadius
Querserv originated with the idea that I wanted to take logging events to not only Mysql but send them offsite if possible sort of like a syslog architecture. Right now Queryserv is in it's infancy but I would like to dual-home logging functionality for EITHER text logging or using QueryServ so that it can be used offsite and queried offsite via a web front-end and whatnot. I wanted to get combat logging, event logging and all kinds of other levels of logging pushed off to this and Derision just so happened to implement it with the LFGuild feature.
|
I didn't realise you intended queryserv to run 'off-site', I just saw it as a convenient way to:
a) Avoid making database calls in the main thread, which I hate, and using queryserv was easier than using the existing zone dbasync thread.
b) Avoid the issue of syncing data between zone processes, again without having to read/write the database in the main thread, when updates to that data could be made in any zone.
I could move the LFGuild stuff out of queryserv and back into zone, but I would want to put it into the async DB thread which would mean writing an easier to use interface to dbasync, which I have thought about off-and-on for a while and would be an interesting exercise.
Another option would be to allow for multiple queryserv processes. When a queryserv process connects, it would tell world which server opcodes it would handle, e.g. you could have a queryserv co-located with world/zones which would say, 'hey, send me all ServerOP_LFGuild packets', and an off-site one which would say, 'send me all logging packets'.
Threaded Mode
