SRV handling of weight and priority is complicated

Bug #785022 reported by François Marier on 2011-05-19
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Melissa Draper

Bug Description

It looks like the priority is handled correctly, but the weight attribute is more of a statistical thing (see RFC2782 weight ordering algorithm on page 3 for the gory details).

You can probably just copy the code from the Perl module (srv_hostname function):

Melissa Draper (melissa) on 2011-05-21
Changed in services-libravatar:
status: New → Confirmed
importance: Undecided → High
Melissa Draper (melissa) on 2011-05-22
Changed in services-libravatar:
status: Confirmed → In Progress
assignee: nobody → Melissa Draper (melissa)
François Marier (fmarier) wrote :

As far as I can tell, it should work.

At least, I can't easily see anything wrong with your code.

Melissa Draper (melissa) on 2011-05-24
Changed in services-libravatar:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers