On Thu, 03 Jan 2008, Tim Ansell wrote: <snip> > My idea with difference lists where that they should return objects > which have changed since X (not necessarily in the order they changed). > > For example, on tpserver-py I would just do a query something like > "SELECT id FROM blah WHERE modtime > diftime". This even works for dead > objects in my case, as once it's dead, it's mod time never changes > again.
While this is fine for tpserver-py, tpserver-cpp does things a little differently. For getting the data from database is no problem. The issue is keeping it, correctly, when not using persistence. > This means you shouldn't need to store anything extra for difference > support. (You may need to store extra information for history stuff, if > in the future we need to figure out which turns an object changed). The actual hard bit is figuring out weather the player's view has changed or not, without doing an expensive field by field comparison. > In the worst case this is just returning a list of all object IDs > (including all objects which have died). In the best case you get no > object IDs. My guess is that around 20%-30% of objects in many universes > will be static (and all dead objects should be static). Dead objects should only be returned once. Vanishing/appearing objects could appear quite often. > Tim 'Mithro' Ansell Later Lee
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
