Or you could as well make a new message, then alternate it with the current one. Eg. instead of sending CoarseLocation update every x (lets say 5 ) seconds,you send 0 - CoarseLocation 5 - CoarseLocationNew 10 - CoarseLocation 15 - CoarseLocationNew
And so on. - Old clients would lose update precision. But not be broken. - New clients would use both messages and get X/Y updates at the same interval as today. For Z they could interpolate if the old message send an 'out of range'-Z value. Or just live with the lower Z update frequency. Both would still be vastly better than what we have now. - The amount of message the simulator has to send would not increase. Phase out the old message by reducing its frequency after a few month, then stop sending it at all. Whoever did not update their code by that time could be considered badly outdated. _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
