Return-Path: X-Original-To: apmail-qpid-users-archive@www.apache.org Delivered-To: apmail-qpid-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 623BE10137 for ; Fri, 3 Jan 2014 18:55:02 +0000 (UTC) Received: (qmail 18972 invoked by uid 500); 3 Jan 2014 18:53:46 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 18934 invoked by uid 500); 3 Jan 2014 18:53:44 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 18905 invoked by uid 99); 3 Jan 2014 18:53:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jan 2014 18:53:42 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of matthew.crinklaw-vogt@lmco.com designates 192.35.35.12 as permitted sender) Received: from [192.35.35.12] (HELO mailfo02.lmco.com) (192.35.35.12) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Jan 2014 18:53:33 +0000 Received: from HVXHTPN11.us.lmco.com (hvxhtpn11.ems.lmco.com [158.186.149.29]) by mailfo02.lmco.com (8.14.5/8.14.5) with ESMTP id s03IrBWa026702 for ; Fri, 3 Jan 2014 18:53:11 GMT Received: from HVXDSP42.us.lmco.com ([fe80::d2d:1f68:2ae2:e072]) by HVXHTPN11.us.lmco.com ([fe80::edb4:3b6e:fd89:3dee%15]) with mapi id 14.02.0318.004; Fri, 3 Jan 2014 13:52:03 -0500 From: "Crinklaw-Vogt, Matthew" To: "users@qpid.apache.org" Subject: qpid 0.24 client with a 0.14 broker Thread-Topic: qpid 0.24 client with a 0.14 broker Thread-Index: Ac8Ip0H7/k2x0+sYT3WmMY69pkPKXA== Date: Fri, 3 Jan 2014 18:52:03 +0000 Message-ID: <0E816A6915031F4387FE5C84DE1D3FC736B69A@HVXDSP42.us.lmco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [158.186.156.83] Content-Type: multipart/alternative; boundary="_000_0E816A6915031F4387FE5C84DE1D3FC736B69AHVXDSP42uslmcocom_" MIME-Version: 1.0 X-LM-Outbound: External 158.186.149.29 cntry=us g=b4de9ffe0a9a06aef10435f7502a1a29 q=s03IrBWa026702 m=1 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-01-03_07:2014-01-03,2014-01-03,1970-01-01 signatures=0 X-Virus-Checked: Checked by ClamAV on apache.org --_000_0E816A6915031F4387FE5C84DE1D3FC736B69AHVXDSP42uslmcocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Since qpid 0.14 and 0.24 both support the same version of the AMQP spec, sh= ould I expect a qpid 0.24 java client to work with the qpid 0.14 C++ broker= ? I assume that if I were to venture out an use features like 'x-bindings' th= at aren't covered in the AMQP spec then I shouldn't expect those to work wi= th different client and broker versions, or would you expect those to work = too? Matt Crinklaw-Vogt Lockheed Martin, MS2 703-367-1040 --_000_0E816A6915031F4387FE5C84DE1D3FC736B69AHVXDSP42uslmcocom_--