Oh, on the multiple instances part, here's another scenerio.
Say you run 3 queries, coping the information into 3 sets of variables before you want to look and see if any failed, you would have overwritten the information from the first two following your theory, but RunQuery as it is now just copies all relevent data into the variables you provide, freeing you to not have to worry about, even in a single thread situation, the order in which you run queries.
I thought about connection pooling and such, but would honestly would use more resources than you'd gain speed by slowing down the server with multiple connections from each world. It would be perfect if you could create a single pool that all zones on a server drew from, but the interprocess communication is difficult there, unless you redid things so you could host multiple zones in the same process space, which has been thought about before, but always died because we dont want a crash of one zone bringing down 20 zones.
You may want to take a look at the AsyncWork objects, they do pretty much what you're talking about, copy all possible information (result set, all functions that'd be run on the mysql variable, etc) into the class and then allow it to be used later.
|