K 10
svn:author
V 6
adrian
K 8
svn:date
V 27
2012-10-26T16:31:12.022417Z
K 7
svn:log
V 471
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.

END