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 69322102D3 for ; Tue, 17 Feb 2015 20:58:53 +0000 (UTC) Received: (qmail 1960 invoked by uid 500); 17 Feb 2015 20:58:53 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 1925 invoked by uid 500); 17 Feb 2015 20:58:53 -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 1914 invoked by uid 99); 17 Feb 2015 20:58:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2015 20:58:52 +0000 X-ASF-Spam-Status: No, hits=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gsim@redhat.com designates 209.132.183.28 as permitted sender) Received: from [209.132.183.28] (HELO mx1.redhat.com) (209.132.183.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Feb 2015 20:58:47 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t1HKuOZI006659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Tue, 17 Feb 2015 15:56:24 -0500 Received: from [10.36.116.68] (ovpn-116-68.ams2.redhat.com [10.36.116.68]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t1HKuMqi002953 for ; Tue, 17 Feb 2015 15:56:23 -0500 Message-ID: <54E3AB5A.1030608@redhat.com> Date: Tue, 17 Feb 2015 20:58:02 +0000 From: Gordon Sim Organization: Red Hat UK Ltd, Registered in England and Wales under Company Registration No. 3798903, Directors: Michael Cunningham (USA), Matt Parsons (USA), Charlie Peters (USA), Michael O'Neill (Ireland) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: users@qpid.apache.org Subject: Re: MUST a send and receive link ALWAYS be set up for a session... References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26 X-Virus-Checked: Checked by ClamAV on apache.org On 02/17/2015 07:37 PM, Tony Ercolano wrote: > I'm having a discussion with someone. > > Using a proton messenger I set up to talk to a service. > I set up with various pn calls to do sends. I do NOTHING to set up to receive. > > When I go to send my data to the service proton will: > @open > @begin > @attach (with handle=0 role=false source=@source(40) target=@target(41)... > Then the service starts talking back then the client sends another > @attach(with handle=1 role=true but no source or target field) > > This seems reasonable to me. There is nothing (as far as proton is concerned) to say about the receive path. It just HAS to be set up because sessions are bi-directional. > > Am I understanding this correctly? Most importantly am I interpreting the AMQP standard correctly? The AMQP standard certainly doesn't mandate that a link must be established in each direction on a session. I assume messenger is establishing the receiving link for some reason (perhaps to receive replies?) but it is a bit odd to initiate a receiving link with neither source nor target. Are you sure its not being initiated by the peer? --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org