History of IdleTimeProtocol

Difference (from prior major revision) (minor diff, author diff)

Changed: 3c3

currently partially implemented by ginsu; client side implemented by vtFugu

Currently implemented by damascus, partially by ginsu, and client side by vtFugu.

Changed: 15c15

the server only needs to send notice.idle fragments not when their idle time changes (since it is constantly changing, or growing at least even if they are not there) but rather when their last known active time changed (and it can do that lazily). a simple algorithm would be to periodically (every few minutes) check whether the users last known active time had changed, and if so resend a new presence notice to _gale.notice.<name>@<domain>. if their last known active time was less than a few minutes ago, send a status.idle (not idle) fragment if one has not been sent already.

the server only needs to send status.idle fragments not when their idle time changes (since it is constantly changing, or growing at least even if they are not there) but rather when their last known active time changed (and it can do that lazily). a simple algorithm would be to periodically (every few minutes) check whether the users last known active time had changed, and if so resend a new presence notice to _gale.notice.<name>@<domain>. if their last known active time was less than a few minutes ago, send a status.idle (not idle) fragment if one has not been sent already.

Changed: 34c34

* does not depend on timliness of server, since the notice.idle contains the absoute time, they can be sent at any point by the server when it realizes one is necisarry.

	Revision 8 . . (edit) February 3, 2003 19:57 by AbeEgnor
	Revision 7 . . January 27, 2003 15:38 by adsl-63-206-233-80.dsl.lsan03.pacbell.net
	Revision 6 . . January 27, 2003 05:58 by 66-108-203-93.nyc.rr.com
	Revision 5 . . December 13, 2002 16:51 by JohnMeacham