comparison ChangeLog @ 27213:3e516701dd33

Changes to our DNS SRV record sorting, care of Vijay Vijay Raghunathan from Meebo. SRV records have two fields that determine the order in which the results should be used: 1. Priority (which we call "pref" for some reason). Records with a lower priority will be used first. 2. Weight. Records with a higher weight are more likely to be used first, but there is some amount of randomness. We were actually doing this backwards and using records with lower weight first. And we weren't randomizing. But now we are.
author Mark Doliner <mark@kingant.net>
date Mon, 29 Jun 2009 06:49:59 +0000
parents bd85e78518b7
children a337d7a5cd0c
comparison
equal deleted inserted replaced
27212:862b8208a546 27213:3e516701dd33
16 * Report idle time 'From last message sent' should work properly. 16 * Report idle time 'From last message sent' should work properly.
17 * Show the invite message for buddies that requested authorization 17 * Show the invite message for buddies that requested authorization
18 from you on MSN. 18 from you on MSN.
19 * DNS servers are re-read when DNS queries fail in case the system has 19 * DNS servers are re-read when DNS queries fail in case the system has
20 moved to a new network and the old servers are not accessible. 20 moved to a new network and the old servers are not accessible.
21 * DNS SRV records with equal priority are sorted with respect to their
22 weight as specified in RFC 2782. (Vijay Raghunathan)
21 * GnuTLS logging (disabled by default) can be controlled through the 23 * GnuTLS logging (disabled by default) can be controlled through the
22 PURPLE_GNUTLS_DEBUG environment variable, which is an integer between 24 PURPLE_GNUTLS_DEBUG environment variable, which is an integer between
23 0 and 9 (higher is more verbose). Higher values may reveal sensitive 25 0 and 9 (higher is more verbose). Higher values may reveal sensitive
24 information. 26 information.
25 27