On Thu, 13 Dec 2007, Lee Begg wrote: > Hi all > > I was working on creating a proper difference list implementation for > tpserver-cpp and realised that they are not actually helpful in at least > one case.
<snip> > For designs, components, categories, object types, order types, resource > types, properties, boards and probably research related frames, there will > be very few changes, but there will also be far fews ids, and therefore the > lists will be shorter. Been working on ComponentView in tpserver-cpp since I wrote this message. I can see how it could be some use to have difference lists. But there is still the same issue when taken to advanced levels. If you have a good spy network, for example, you might be able to see changes to the number of a design every turn. The group above is fundamentally different from objects. You can only gain knowledge in the group, and it tends to be quite slow. Objects change in multiple ways each turn. Another thing is that I feel that the difference list is a little bit underspecified. Are duplicate ids allowed in the difference list? Is there a limit to the list? > Any thoughts? Ideas? Suggestions? Rants? > > Later > Lee Replying to myself looks funny. 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
