On Saturday 17 March 2007 01:10, Lee Begg wrote: > On Thursday 15 March 2007 16:10, Tim Ansell wrote: > > On Thu, 2007-03-15 at 00:17 +1300, Lee Begg wrote: > > > Object Parametrisation/Last seen - Default order queue id > > > > > > The Default order queue will only be used as a transition mechanism. A > > > client implementing should not assume that the default order queue has > > > the same id as the object. > > > > I think it should be permanently this way. Is there any reason not to do > > this? > > If you have objects with two (or more) queues, what id do you put on the > later one? How do you leave enough space (id numbers) for future object's > queues?
I have a better idea. Why not have a flag to say if the queue is "active" (in the object parameter)? What does having a "Default queue id" mean anyway? As a transition mechanism it's ok, but other than that? > > > Position Object Parameter Type > > > > > > The current description only allows an object to be free or bound and > > > not change between them. I think we will need to be able to do that... > > > > Can you think of a good way to do this? > > A suggestion might be: > <byte position type> > if the position type is 0 then three 64 bit ints follow for free space, > otherwise it's bound. Humm... you could put a 3d position and a bound position as parameters, and then have some way of telling when it is bound and when it is free. > > > Later > > > Lee > > > > Tim Ansell > > Later > Lee I am working on writing them into the protocol.xml document. Later Lee
pgpoltWwPfO97.pgp
Description: PGP signature
_______________________________________________ tp-devel mailing list [email protected] http://www.thousandparsec.net/tp/mailman.php/listinfo/tp-devel
