On Mon, Dec 04, 2006 at 07:45:54PM -0500, Reed Hedges wrote: > 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.)
Yes, the idea was a clock is a vobject that would include a) a "real clock" that advanced in real time (and thus would require a time synchronization protocol) b) a "virtual clock" controlled in software that is advanced explicitly c) the time is defined in terms of a linear time transform applied to the output of another clock vobject. [ Peter Amstutz ][ [EMAIL PROTECTED] ][ [EMAIL PROTECTED] ] [Lead Programmer][Interreality Project][Virtual Reality for the Internet] [ VOS: Next Generation Internet Communication][ http://interreality.org ] [ http://interreality.org/~tetron ][ pgpkey: pgpkeys.mit.edu 18C21DF7 ]
signature.asc
Description: Digital signature
_______________________________________________ vos-d mailing list vos-d@interreality.org http://www.interreality.org/cgi-bin/mailman/listinfo/vos-d
