On Tuesday 03 April 2007 19:19, Brett Nash wrote: > > Getting a Sequence > > ... > > > If the client requests any of the following a Fail packet will be > > returned (as they are a violation of the requirements specified > > above). > > * a range has already had any part already given (IE no > > overlaps) > > * a range specifies a range which starts below the previously > > ending number (IE requesting from 6 to 10 then 0 to 5) > > * a range is bigger then the remaining IDs left (IE requesting 6 > > when only 4 remain) > > * try to use a key from a previous connection
Despite the instance in the protocol doc, tpserver-cpp doesn't do this. tpserver-cpp allows overlaps, and any range, and if the range is bigger that available just returns what it has. It only updates the key when the state in the server changes, and does warn if the key is wrong. > These 4 errors all need specific error codes. The default action on a failure of a GetIdSequence base frame is to try again with '-1' (new) key. > This was the sort of thing I was complaining about earlier. All > specific failures should really have their own error code. > > Also each frame should list any error codes it can return. > > You may want to split the error codes too: > < 0x1000 can occur any frame (as short a list as possible) > - protocol error > - frame/framing error > - Server is farked error > 0x1000 + Other errors, per message. Not a bad plan. Later Lee
pgpfzpi8YCKq3.pgp
Description: PGP signature
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
