[ https://issues.apache.org/jira/browse/DISPATCH-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross updated DISPATCH-798: ------------------------------ Fix Version/s: 1.0.0 > Policy description in Dispatch Router book seems to be incorrect > ---------------------------------------------------------------- > > Key: DISPATCH-798 > URL: https://issues.apache.org/jira/browse/DISPATCH-798 > Project: Qpid Dispatch > Issue Type: Bug > Components: Documentation > Affects Versions: 0.8.0 > Reporter: Kai Hudalla > Fix For: 1.0.0 > > > Hi, > example 4 from section 3.6.5 of the Dispatch Router book seems to be > incorrect in that it suggests that the *maxSessionWindow* can be used to set > the number of frames that can be buffered unsettled. However, from a recent > discussion on the mailing list [1], my understanding is that > *maxSessionWindow* needs to be set to the total number of bytes that can be > buffered, i.e. maxSessionWindow = maxFrameSize * number of frames to buffer. > Section 4.4.3 on configuring listeners actually describes how > *maxSessionFrames* can be used to set the maximum number of frames to buffer > in a session. To me this is the more user friendly approach (since it leaves > the calculations to the machine) and should be adopted in the policy > definition as well. > [1] > http://qpid.2158936.n2.nabble.com/Dispatch-Router-throughput-tp7664757.html -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org