[vos-d] Sector clock

[Reed Hedges]

Peter Amstutz wrote:

>> Oh, btw... we are speaking of a "server" here, but VOS is still  
>> conceptually P2P, even if in practice it degenerated to client-server  
>> due to firewall issues. Time coordination among peers is nasty; I'd  
>> suggest the site hosting the sector vobject should act as a time  
>> coordinator (read "server" above) then.
> 
> Yes, that's just what I was thinking.


Well, it doesn't have to be the sector itself, it should be a "clock"
vobject associated with it, and the client uses the clock for it's
current sector that it's "in".   That way you could have a common clock
for some closely connected sectors.  Or use a seperate server from the
sector server for the clock, for load balancing reasons or whatever (or
attempt fancy tricks behind the scenes with multiple clock servers for
extremely busy sectors.)

VOS should always allow options and flexibilty :)

Reed