Thanks for the summary. A few notes inline. On Sunday 21 January 2007 20:08, Tim Ansell wrote: <snip> > * EOT Notification > > A new frame will be added to allow clients to request that a turn be > ended. The Time Remaining frame will had a new field added which > explains why this Time Remaining frame was sent. > > This should allow the following cases, > - EOT when everyone finished. > - EOT at timeout. > - EOT after short timeout when majority finished. > > For example, say 6 players are playing. After 4 players submit > "Finished" frames, the other players get a "Time Remaining frame" with, > say, 2 minutes left and an ID which says "All other players finished".
What should the EOT time be for the first case, and for the last case before the majority is finished? > * Difference support > > The Get ID's frames will have a "from" field added. This is a SInt64 > which is the timestamp to get changes from. If it is -1 then it should > be all objects. > > It is important to note that the Get ID's frame when called with a valid > time stamp, the server should send ID's for objects which may have been > destroyed or no longer exist. Humm.... I don't think that is quite right. But if it is, the frame type version for the Get Ids frame is 1, and the corresponding reply could have a frame type version of 0, indicating the full list *without* deletions. > * Frame type Versioning > > The TP03 header will be changed to a "TP<major byte><minor byte>". The > major byte is the version of the protocol (for example 1, 2, 3, 4). > > Minor byte is the minor revision of the frame. As new versions of frames > are added the minor byte will be incremented. (They all start at zero.) > > A frame will not change in an non-backwards compatible way within a > major protocol. The major byte can be 3, for tp03 with frame type versioning and header and all minor bytes are 0. tp04 with major 4 and minor 0 is the same as tp03 with new header. <snip> > * History Support > > History support will wait till tp05. But should be stored server side in preparation for tp05. > * Async Frames > > If something changes on the server is can send a frame at any time > saying so. This is mainly used when a creating a Design might add a new > component. (For example, creating a new Torpedo design would create a > new Torpedo design.) Currently only components are on this list (other than the time remaining frames). Once research/technology is implemented, there could be others. I would rather have a set list. > * Research / Technology Frames > > A new frame will be added which describes things which can be > researched. The standard get ids, etc frames will be added for these > objects. This frame will have at least the following, > - Name > - Description > - Generic Reference System List of things which this technology brings > > Each technology which describe which technology it depends on and which > technology is an anti-dependency. How these dependencies are described > is yet to be figured out. Open discussion here...... > Tim Ansell Thanks mithro for typing this up. If anyone thinks there is anything wrong with any of this, or has any suggestions, let us know. Later Lee
pgpVe8aHCKXLv.pgp
Description: PGP signature
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
