Ok. I've had a look and here is a few comments. As of TP04, the primary identity of a queue of orders is now the "Order Queue ID", instead of the Object id. I think we should continue to use the Order Queue, they could even be promoted to first class protocol objects (and use the flags already available in tpserver-cpp, such as repeating and inactive).
Internally, tpserver-cpp assigns a id to each order, and orders the ids for the actual queue. The ids are unique within an order queue. This is possibly another thing to use. Can we make insert simple to append only, and then use reorder to get in it the right order? Can think of a different way for name things because "reorder and ordering orders into the right order" is hard to understand? :-) Any of this helpful? Later Lee On Thu, 24 Jan 2008, Brett Nash wrote: > I'll add to wiki once the first round of flaming has completed ;-) > > Please find attached document. It probably needs some tweaking, but I > think the core idea is valid. > > It's a bit more complex then the current version but it: > - Avoids the needs to serialise things > (eg multiple deletes or inserts). > - Allows order caching > - Allows smaller insertion messages > - Requires fewer messages > - Saves messages for small changes > > One outstanding issue is when to know the specific order desctiption is > out of date. > > My currnet thinking is to add a last changed field to the orderid, > version# list in current orders (so you can see it's changed there). > However I fear for non-trivial games it will need updating every turn > anyway :-( > > Regards, > nash
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
