From qpid-users-return-439-apmail-incubator-qpid-users-archive=incubator.apache.org@incubator.apache.org Mon Nov 24 09:54:36 2008 Return-Path: Delivered-To: apmail-incubator-qpid-users-archive@locus.apache.org Received: (qmail 62062 invoked from network); 24 Nov 2008 09:54:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 24 Nov 2008 09:54:36 -0000 Received: (qmail 38191 invoked by uid 500); 24 Nov 2008 09:54:46 -0000 Delivered-To: apmail-incubator-qpid-users-archive@incubator.apache.org Received: (qmail 38174 invoked by uid 500); 24 Nov 2008 09:54:46 -0000 Mailing-List: contact qpid-users-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: qpid-users@incubator.apache.org Delivered-To: mailing list qpid-users@incubator.apache.org Delivered-To: moderator for qpid-users@incubator.apache.org Received: (qmail 66786 invoked by uid 99); 24 Nov 2008 06:46:46 -0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of uname32@gmail.com designates 209.85.146.182 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=P+90APTeSDu3F0hrh5EXix8HWrh+QL5WJWQYr5tH4Ow=; b=Yxb12aZSiISMqUpNHbUap9lYl0lp7ocL3FRSRiIkC2onhGEy9fVN1fuedFY0XTUXtu l+1EfuyCB85l62+XNlvHz63ndWNnj/JpKhv0GFJxKMBsdsBkKZx9AHY/iYETCwJZmYsH ktgzcnXj+OVy+Fi4aV+lDrMojdZ5DUFFoc/bI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=nPRdkt+Ucitm/B3qYZMpYbhHMWIRugpFN4MoORhj3LDorD9vKHE+yiuXqm7FoXK50I uN0+tDSkzFnx0JvVrlu6qeuru79nIcYoPUqXYU9vUF5HxpVmGc6fxj+dsEMaVJqi2uky P4lojd/5ThLiUSNkT9QZudex/NIycpLFqO9+I= Message-ID: <71d902100811232246u160fbe46n36dfad9cbe2828bc@mail.gmail.com> Date: Mon, 24 Nov 2008 01:46:07 -0500 From: "M Q" To: qpid-users@incubator.apache.org Subject: C++ client API help MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_119129_7905659.1227509167075" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_119129_7905659.1227509167075 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline How can I get the qpid C++ client API to do the following: * A producer is sending a stream of messages to a single message queue. Each message represents a unit of work to be processed by a computational cluster. The producer's messages must accumulate on a single FIFO message queue, called the work queue. * The cluster of consumers read messages off the queue (round-robin style). The consumers process each message and output the results onto some message queue (called the response queue). * If a client takes a message off the work queue and fails to create a response in a given amount of time then the message must be put back on the work queue. For example, the client might accept the unit of work and then crash. The unit of work must still be completed so it must be returned to the work queue for processing by another client. For example, I might have a series of images that need to be processed by a server farm. Each server can processes the images and I want to distribute the workload across multiple servers. And of course I want all images to be eventually processed, even if one of the severs fails at some point in the process. In terms of the QPID C++ API, how would this work? Should I use reply-to headers in the work queue messages? Can qpid take care of detecting time-outs and putting failed work requests back onto the work queue? ------=_Part_119129_7905659.1227509167075--