Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 10710 invoked from network); 10 Nov 2009 13:57:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Nov 2009 13:57:22 -0000 Received: (qmail 22144 invoked by uid 500); 10 Nov 2009 13:57:22 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 22123 invoked by uid 500); 10 Nov 2009 13:57:22 -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 22113 invoked by uid 99); 10 Nov 2009 13:57:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 13:57:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of esjewett@gmail.com designates 209.85.160.41 as permitted sender) Received: from [209.85.160.41] (HELO mail-pw0-f41.google.com) (209.85.160.41) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Nov 2009 13:57:14 +0000 Received: by pwj1 with SMTP id 1so23438pwj.20 for ; Tue, 10 Nov 2009 05:56:53 -0800 (PST) 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:message-id:subject:from:to:content-type; bh=Zdfkklgp+iHfvkw7pdCPFEkqDDbQ9QcSwf2JnBDe6AY=; b=ObE4k0z+ocLFH2p9zjay8ePGm58dvefdfseYfsvezotXE0FDcBbYcXsLEhHpdE8mJ1 7s9ctfV9FFrH+VBjukNvD6Pt4+VVMcHBeZps1IRJcjoyExzXvn9rsENpcrUeaHUnsm/Z 42gCeKPD9Ww+l2pFO6Vimjp64xEsbPjky2YJA= 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=q6ENTpmkavRkxe5L/5Sq7mibec1rxXFE7oiZyJUMOZmkJEXMCMP5u+ghVbbPjF/Kfo vJ80OEwTRDWR1dewkHyy9u0K+lADUd/FNSJCWIvbAtyTW6eW1gDgZha0FYV2IAkT70NT r6y2USOtD+Q59HOerU5VqHVqe3DHtcly58jMc= MIME-Version: 1.0 Received: by 10.141.29.17 with SMTP id g17mr3906rvj.211.1257861413189; Tue, 10 Nov 2009 05:56:53 -0800 (PST) In-Reply-To: References: <68f4a0e80910270655g77db6321m53f8757a9ab115b2@mail.gmail.com> <68f4a0e80910290938x2614b4e6r5a4e05fa69f0ebb2@mail.gmail.com> Date: Tue, 10 Nov 2009 08:56:53 -0500 Message-ID: <68f4a0e80911100556q23fc9b37m68d7e3a056a3c078@mail.gmail.com> Subject: Re: Actions, tags, and the public timeline From: Ethan Jewett To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Just bumping this up again, as I kind of forgot about it. Vassil, what would this syntax to specify a tag or pool for a new message look like? I assume it would be different for resend vs. messages generated from feeds. Maybe we can work out what the action command should look like and then create a JIRA ticket for it. Ethan On Fri, Oct 30, 2009 at 4:58 AM, Vassil Dichev wrote: >> I think the idea of specifying a pool for the results of an action is >> good idea. We just need a new action "resend [pool] -- sends the >> message to a particular pool" > > Not exactly. First of all, on the ESME specification or on the mailing > list there was a specific requirement *not* to move a message from one > pool to another automatically- only by a very explicit copy/paste by > the user. Second, the messages from Atom/RSS are not "resent", there > is an actor started which creates and sends them automatically. > > I had an idea in the past to specify a tag to apply on all messages > created from a feed in order to be able to filter it. Later there was > also the idea to be able to specify a pool, too. Maybe that's what you > meant, and it's a great idea. >