Return-Path: Delivered-To: apmail-qpid-users-archive@www.apache.org Received: (qmail 54824 invoked from network); 16 Aug 2010 15:52:59 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 16 Aug 2010 15:52:59 -0000 Received: (qmail 74195 invoked by uid 500); 16 Aug 2010 15:52:58 -0000 Delivered-To: apmail-qpid-users-archive@qpid.apache.org Received: (qmail 74168 invoked by uid 500); 16 Aug 2010 15:52:58 -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 74160 invoked by uid 99); 16 Aug 2010 15:52:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Aug 2010 15:52:58 +0000 X-ASF-Spam-Status: No, hits=4.4 required=10.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of koolvivek2006@gmail.com designates 209.85.215.42 as permitted sender) Received: from [209.85.215.42] (HELO mail-ew0-f42.google.com) (209.85.215.42) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Aug 2010 15:52:52 +0000 Received: by ewy2 with SMTP id 2so3282770ewy.15 for ; Mon, 16 Aug 2010 08:52:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=leOAe2CPEafQI8V9pjp68LXRushKefbwMjNA3ru3kh8=; b=Kl0hEEB1H1CUzVoIiI152KNrbZJ8TY73pmeFYkV8aCKeB7dluTl0pYY6KhC/stF7X0 LQcJWkgE2hDoYEszbQoOqNgG6B/HOK+0hiR5AcncwIxB6KLIkCoMCPsUS/twF0jxIFKD Uyw369naYBE/Qj14T2pR8w+S91sakTx8r2LJU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=FidiwSDtkrXgVeTz8UE2ImTsZQgCGmBqOt/D1iy5IyexbLn6IkY/FmSDk22qQP2p15 O+UYIp7KvltRdvX9XaC3TaWerVhuN76G/36qKrD5/Y07dnjj6pnd7Xxe2WhgsqKD0wk7 gsOPB+HbG7HG3DPJbRyUu4CY4jpsrpRLy/1H4= MIME-Version: 1.0 Received: by 10.213.13.137 with SMTP id c9mr5113565eba.41.1281973950472; Mon, 16 Aug 2010 08:52:30 -0700 (PDT) Received: by 10.14.22.1 with HTTP; Mon, 16 Aug 2010 08:52:30 -0700 (PDT) In-Reply-To: References: <4C62B90E.5010301@redhat.com> Date: Mon, 16 Aug 2010 21:22:30 +0530 Message-ID: Subject: Re: Comparison with RabbitMQ From: vivek agarwal To: users@qpid.apache.org Content-Type: multipart/alternative; boundary=0015174c14c4ede457048df2d178 --0015174c14c4ede457048df2d178 Content-Type: text/plain; charset=ISO-8859-1 So, suppose, if I provide a API for my users to access Qpid, and allow them to dequeue data and I send the data back over the network to them. Now unless, they acknowledge that they have processed the data, I may receieve thousand such requests (or more). I want to keep the data around, but would not be able to maintain the track of session object for each such dequeue request. I dont want my users to worry about using qpid, so I give them very simple API abstracting the details of connection, connection factory and all this. I think this is not a very rare use-case, and I would like to know, if there is any work around for acknowledgment in such situations. Thanks, Vivek On Mon, Aug 16, 2010 at 9:08 PM, Rajith Attapattu wrote: > On Mon, Aug 16, 2010 at 6:23 AM, vivek agarwal > wrote: > > Hi, > > > > Do we have a API for direct AMQP over Apache Qpid, instead of going > through > > JMS? > > We have through experience found out that most use cases can be met > with pure JMS + configuration. > The new addressing syntax give the JMS user a lot of flexibility in > leveraging the AMQP features. > Another benefit is that you could easily switch to another AMQP > version or another vendor that supports JMS without having to change > code. > The C++ and Python clients have also started to support a high level > messaging API instead of something very close to the protocol. > It allows a developer to think more in high level messaging concepts > instead of worrying about every detail of the protocol. > > If you are unsure, please feel free to discuss your use cases and we > are happy to help you in figuring out the configuration etc. > > > Also, I wanted to enquire if its implements AMQP .10 fully. > > Yes, the Qpid JMS client implements the 0-10 version. > > > I have a very specific use-case, where a consumer may consume a message, > and > > acknowledge it after a long processing. So can it be done without keeping > > the Session object ( through which I received the message) open? > > You can use the client ack mode in JMS for this. > But whether you use JMS or an API closer to the protocol, you still > need to keep the session object open as the message delivery was done > within the context of that session. > May I know what your concern is in keeping the session object around? > > > Thanks, > > Vivek > > > > > > On Wed, Aug 11, 2010 at 8:21 PM, Gordon Sim wrote: > > > >> On 08/11/2010 03:27 PM, Rajith Attapattu wrote: > >> > >>> On Wed, Aug 11, 2010 at 9:57 AM, vivek agarwal > > >>> wrote: > >>> > >>>> Hi, > >>>> > >>>> Thanks for the reply. > >>>> We are planning to use a Java broker as most of our applications are > in > >>>> Java. Will this affect performance? > >>>> > >>> > >>> As Gordon mentioned, please try both the Java and C++ broker and see > >>> what fits your needs. > >>> > >> > >> Actually I just said try out the Java broker (as that was your preferred > >> option) to confirm it meets your needs (I believe it will). > >> > >> Not that I'd want to put you off trying the c++ broker out as well of > >> course if you have the interest :-) > >> > >> > >> --------------------------------------------------------------------- > >> Apache Qpid - AMQP Messaging Implementation > >> Project: http://qpid.apache.org > >> Use/Interact: mailto:users-subscribe@qpid.apache.org > >> > >> > > > > > > -- > Regards, > > Rajith Attapattu > Red Hat > http://rajith.2rlabs.com/ > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:users-subscribe@qpid.apache.org > > --0015174c14c4ede457048df2d178--