Ok, I'm in favor of including this for 0.10 as long as the user is tipped off somehow via the release notes.
-Steve > -----Original Message----- > From: Gordon Sim [mailto:[email protected]] > Sent: Monday, March 07, 2011 7:54 AM > To: [email protected] > Subject: Re: QPID-3115: candidate for 0.10? > > > On 03/07/2011 12:32 PM, Steve Huston wrote: > > Hi Gordon, > > > >> I have completed fixes to the c++ client for QPID-3115 (making it > >> more consistent with the python connection options). > >> > >> I believe this is a low risk set of changes and would be useful to > >> users of Qpid 0.10 and would therefore suggest they could be merged > >> on to the > >> 0.10 release branch. However they are not critical in anyway, > >> so this is > >> not essential. > >> > >> Any thoughts or opinions? > > > > Consistency is good. Is there any place the change is > documented for > > the unsuspecting user? > > I've update the programming guide in line with these changes. > However it > doesn't describe the change itself, just the final state. I think the > JIRA (and thus release notes) would be the best place to describe the > change. The commit logs attached to the JIRA do that to some > extent, but > I can add an explicit comment also. > > > Will this break 0.8 applications? > > The old names are still supported. However where previously > unrecognised > options were silently ignored, now they will cause an exception. > > --------------------------------------------------------------------- > 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]
