Adrian Chadd 9572684af7 Since it's not immediately obvious whether the current TX path handles
fragment rate lookups correctly, add a comment describing exactly that.

The assumption in the fragment duration code is the duration of the next
fragment will match the rate used by the current fragment.  But I think
a rate lookup is being done for _each_ fragment.  For older pre-sample
rate control this would almost always be the case, but for sample
it may be incorrect more often then correct.
2012-10-26 16:31:12 +00:00
..
2012-10-10 08:36:38 +00:00
2012-10-24 18:21:22 +00:00
2012-09-14 22:00:03 +00:00
2012-10-10 08:36:38 +00:00
2012-10-23 02:20:11 +00:00
2012-10-10 08:36:38 +00:00