On Thu, 17 Jan 2008, Tim Ansell wrote: > <snip> > > > > 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? > > If this is not always going to be this way, I don't we should support it > as a transition mechanism.
This is what tpserver-cpp does: Objects can have one or more orderqueues, their behaviour is exactly as TP04 states. For TP03, the server looks up the object, finds the first queue id for that object, and then uses that internally. There is no need for worrying about "default" queue ids. > > > > > 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. > > I think recent discussion means we need to another look at the bound > position type. Yes it needs discussion. > <snip> > > Tim 'Mithro' Ansell 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
