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 AB1B8107C2 for ; Wed, 28 May 2014 15:45:54 +0000 (UTC) Received: (qmail 24747 invoked by uid 500); 28 May 2014 15:45:54 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 24706 invoked by uid 500); 28 May 2014 15:45:54 -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 24698 invoked by uid 99); 28 May 2014 15:45:54 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 May 2014 15:45:54 +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 (nike.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; Wed, 28 May 2014 15:45:50 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s4SFjOhs013450 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 28 May 2014 11:45:24 -0400 Received: from [10.36.116.65] (ovpn-116-65.ams2.redhat.com [10.36.116.65]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s4SFjNaO005281 for ; Wed, 28 May 2014 11:45:24 -0400 Message-ID: <53860489.2020700@redhat.com> Date: Wed, 28 May 2014 16:45:13 +0100 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: AMPQ 1.0 brokerless P2P connection (qpid 0.26, proton 0.6) References: <538450F9.5090301@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-Virus-Checked: Checked by ClamAV on apache.org On 05/27/2014 03:56 PM, Alexander Yakovets wrote: > I agree it looks like qpidmessaging.dll from qpid 0.26 with proton 0.6 do > not support listening for incoming connection client but maybe future > versions will be capable for this? Does qpid architecture suppose this > functionality? Or any communication via qpid::messaging API must include > broker? In theory it would certainly be *possible* to extend qpid::messaging to allow incoming connections to be listened for and handled. Better non-blcoking support would be needed as well. There is no plan as yet as to if or when this would be done however. Would the proton Messenger API meeet your needs? Note that you could implement the 'server' with Messenger and the 'client(s)' with qpid::messaging if desired. You may have seen my attempts to start a debate about the future direction for the various APIs. If you can share any more detail about what you want from an API and about your use case in general that would be interesting. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org