06-22-09, 06:38 AM
|
#11
|
A Chromatic Dragonspawn
Join Date: Jul 2007
Posts: 196
|
Originally Posted by honem
It really depends on what sort of data is gotten from the server , how big it is and how often it's queried.
With Millions of players I think you can understand that even the smallest amount of data transferred can quickly add up to a lot of data to be transferred.
You'd want it designed in such a way as it doesn't bring a server to it's knees when the entire wow population of a server all logon and click their "check quests complete" button. Even worse if they decide to do it every 5-10 minutes or so.
Maybe a system where you have to request a token from the server before running the query. And the query just sends up a list of quest ids and gets an array of boolen values back. The token you get from the server could be pretty much a "yes you can ask me now" or a "no i'm busy" sort of thing.
|
"That makes sense... so give us an event, Blizzard!"
|
|
|