Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 39021 invoked from network); 13 Apr 2010 13:40:34 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 13 Apr 2010 13:40:34 -0000 Received: (qmail 54248 invoked by uid 500); 13 Apr 2010 13:40:34 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 54188 invoked by uid 500); 13 Apr 2010 13:40:34 -0000 Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: esme-dev@incubator.apache.org Delivered-To: mailing list esme-dev@incubator.apache.org Received: (qmail 54179 invoked by uid 99); 13 Apr 2010 13:40:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 13:40:34 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=AWL,FREEMAIL_FROM,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 esjewett@gmail.com designates 209.85.160.47 as permitted sender) Received: from [209.85.160.47] (HELO mail-pw0-f47.google.com) (209.85.160.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Apr 2010 13:40:28 +0000 Received: by pwj5 with SMTP id 5so4865921pwj.6 for ; Tue, 13 Apr 2010 06:40:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type :content-transfer-encoding; bh=GQlBLQQ041eP9EKEzuCsQ22pCrx6sIgArUlez/ul1Sw=; b=g57jmdYkllwRMByI+krK4NwO2p2aFtZRtMGZZKKWn+Fh8T8rtUh3U++KAcBCrByV9U v1uXWruHMKFipxF2GteamwXnDivuYICk1sc1HyGff/J7CX1IhqJbu83UNRv8KppKf6iw 9UZDc2KbbBcIBvVtkvi0321CT1E4g34WdQUdM= 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:content-transfer-encoding; b=VPk3Rtad74Nk9HwoKo011mcQwRk4gIYG/kYWzAGTfWs9+TfWhsVGpk9I+sOrHRegio n+URHR+3u/qd6AxaLYUEgA+Vmrr7f3DPmeGU/eFnX3Es6zG3J8vB4cLP1JDhQxYGxUNs 5/VIM7c0xR5wxKIXMGX7JRQufZ25KK/Lku8oc= MIME-Version: 1.0 Received: by 10.140.126.12 with HTTP; Tue, 13 Apr 2010 06:40:07 -0700 (PDT) In-Reply-To: References: Date: Tue, 13 Apr 2010 09:40:07 -0400 Received: by 10.141.124.21 with SMTP id b21mr5117630rvn.267.1271166007434; Tue, 13 Apr 2010 06:40:07 -0700 (PDT) Message-ID: Subject: Re: A few requests and few bugs From: Ethan Jewett To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Apr 13, 2010 at 9:13 AM, Richard Hirsch wro= te: > > But we've used actions with tag-based tests in the same way. =A0For examp= le, > in the akibot and 12sprints integrations. After reading the Jira ticket it makes more sense to me. I took this as asking for an action that waits for a particular message and then does something. But you are actually asking for an action that waits for *replies* to particular messages and does something. What I'm wondering now is whether we want to test on the message being replied to or the conversation associated with the message. What do you think? I'm thinking that the conversation makes more sense, because it will catch replies to replies, for example. Depending on what the developers are trying to accomplish, there may also be ways to use the API to do this. Ethan