On Thu, 17 Jan 2008, Tim Ansell wrote: > <snip> > > > Therefore, the added complexity for the difference lists IMHO isn't > > worth the > > trouble. Is there a smarter way? Especially for Objects. > > The biggest problem with objects at the moment is that they change every > time their contents change. This is caused by the fact that we choose to > have objects specify their children rather then children specify their > parents. > > The reason this feature was done was to that somebody could recursively > walk down the universe tree requesting children IDs. Since we now have > both difference lists and Get ID Sequences (both which didn't exist when > this decision was made) and we are making fundamental changes to the > objects anyway, it would be a good time to re-evaluate this decision. > > If instead objects specified their parents, it would drastically reduce > the number of objects which need to be updated. Things which are static > like star system in many rulesets would only ever have to be downloaded > once! > > What do you think?
That's a good idea. I guess the protocol/client libraries would re-create the tree (and therefore the children lists) as necessary. And I know that tpserver-cpp will need to continue to track them (but fun enough doesn't store it in the database). It would also make the Object frames smaller. Oh, and in TP04, Objects do specify their parents (it was requested by nash). We need to make up our minds about removing the children list before I release tpserver-cpp 0.5.0 though (please!). > 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
