Fyi - attached a short doc describing the user interface for this feature. https://issues.apache.org/jira/browse/QPID-2935
Feedback enthusiastically welcomed. -K ----- Original Message ----- > I've just merged the QPID-2935 branch into trunk. > > I'll update the JIRA shortly, and attach some documentation describing > the U.I. as it currently stands. > > Feedback/issues, etc - let me know. Thanks, > > -K > > ----- Original Message ----- > > Hi, Ken. > > > > I think the compromise you've struck with clustering is sensible > > for the 0.10 release. If the work to make flow control work with > > clustering is minor, we may be able to include it as a bug fix in > > 0.10. > > If, otoh, the work required is more extensive, we can address it in > > 0.12. > > > > Either way, I think it's a "go". > > > > Justin > > > > On Thu, 17 Feb 2011, Ken Giusti wrote: > > > > > 10^6 apologies for not weighing in sooner... > > > > > > Regarding qpid-2935: > > > > > > Currently, standalone broker flow control is 'code complete' - it > > > is > > > passing a set of new unit tests I've added. > > > > > > I've run into some problems replicating state when using flow > > > control in a clustered broker. Alan's is helping out here, but for > > > now I've automatically disabled flow control when a broker is a > > > member of a cluster. > > > > > > I've just resync'ed to trunk and refactored to use Gordon's "queue > > > observer" api - all work is currently on branches/qpid-2935 - and > > > "make check" looks good. > > > > > > Other than the cluster issue, I've got a couple of small cleanups, > > > like verifying the cmake + windows build. > > > > > > Worst case, if we cannot get a solution in place for clustered > > > brokers soon, would it be acceptable to allow 0.10 to support > > > producer flow control for only for non-clustered brokers? > > > > > > > > > -K > > > > > > ----- Original Message ----- > > >> Hi, folks. Our schedule (appended below) calls for all major > > >> features > > >> to > > >> be functionally complete and on trunk by the 16th, this > > >> Wednesday. > > >> > > >> This means we are rapidly approaching the point where we make > > >> choices. > > >> If > > >> something won't be ready in time, we need to kick it to the next > > >> release. > > >> > > >> We can make exceptions for changes that don't threaten to > > >> destabilize > > >> the > > >> release. If you'd like an exception, it's quite important that we > > >> discuss > > >> it now. > > >> > > >> I'll begin running the release scripts tomorrow in order to > > >> discover > > >> any > > >> new issues for the alpha release. > > >> > > >> Thanks, > > >> Justin > > >> > > >> --- > > >> > > >> 0.10 feature and improvement jiras: > > >> > > >> http://bit.ly/h3Q7Sk > > >> > > >> 0.10 schedule: > > >> > > >> 16 Feb > > >> > > >> - Alpha > > >> - Trunk remains open > > >> - Feature integration ends > > >> - The alpha release tests the release process after the > > >> introduction of major features > > >> > > >> 2 Mar, 2 weeks later > > >> > > >> - Beta > > >> - Branch for release (trunk remains open) > > >> - Release branch commits require approval > > >> - Release manager produces outstanding bug report, triages bugs > > >> > > >> 16 Mar, 2 weeks later > > >> > > >> - RC1 > > >> > > >> 23 Mar, 1 week later > > >> > > >> - RC2 > > >> > > >> 30 Mar, 1 week later > > >> > > >> - RC3 > > >> - Targeted release date > > >> > > >> > > >> > > >> > > >> > > >> > > >> --------------------------------------------------------------------- > > >> Apache Qpid - AMQP Messaging Implementation > > >> Project: http://qpid.apache.org > > >> Use/Interact: mailto:[email protected] > > > > > > --------------------------------------------------------------------- > > > Apache Qpid - AMQP Messaging Implementation > > > Project: http://qpid.apache.org > > > Use/Interact: mailto:[email protected] > > > > > > > > > > --------------------------------------------------------------------- > > Apache Qpid - AMQP Messaging Implementation > > Project: http://qpid.apache.org > > Use/Interact: mailto:[email protected] > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
