Return-Path: Delivered-To: apmail-incubator-esme-dev-archive@minotaur.apache.org Received: (qmail 97863 invoked from network); 30 Oct 2009 09:59:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 30 Oct 2009 09:59:18 -0000 Received: (qmail 23260 invoked by uid 500); 30 Oct 2009 09:59:18 -0000 Delivered-To: apmail-incubator-esme-dev-archive@incubator.apache.org Received: (qmail 23209 invoked by uid 500); 30 Oct 2009 09:59:18 -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 23199 invoked by uid 99); 30 Oct 2009 09:59:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Oct 2009 09:59:18 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of vdichev@gmail.com designates 209.85.219.205 as permitted sender) Received: from [209.85.219.205] (HELO mail-ew0-f205.google.com) (209.85.219.205) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Oct 2009 09:59:16 +0000 Received: by ewy1 with SMTP id 1so2576570ewy.27 for ; Fri, 30 Oct 2009 02:58:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=VBZ9+qDkq7+PPp+vLVXzDzfe6di1kbtUkwmnCr0O64E=; b=DQlbHm9Pc9tsythxofolAyke21rVu4YJqxkTLI+Ayr+vZCq2RryckVgKK1ZilWYL0p y8hWacFYY5jXnPooA6OsgwJS7E1a4Bp1ZkZ1X4eM0Ndx/u6BIoHRJ2TqjvuKeZqNyTaq wfro19eyv/2XuPVgVm0ERZHfXPVfRutP81lvA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=l5oFKoImgQCAXZKQtD8PG/x/EH95wc+jk2JXTiE7e74PuQNd+qy6eeud0KntdfOYtP N2mPGjxX1vlcI361G4cCoJ8X2WQ72Wiscw5euICo2yWWK1GZVq2zi7wes4YN8EX56GqD JpyJ6RHX9CPQ3gLz2Ma7FwkRY/oM8Sl/lnWqo= MIME-Version: 1.0 Sender: vdichev@gmail.com Received: by 10.216.93.81 with SMTP id k59mr490567wef.169.1256896734877; Fri, 30 Oct 2009 02:58:54 -0700 (PDT) In-Reply-To: References: <68f4a0e80910270655g77db6321m53f8757a9ab115b2@mail.gmail.com> <68f4a0e80910290938x2614b4e6r5a4e05fa69f0ebb2@mail.gmail.com> Date: Fri, 30 Oct 2009 11:58:54 +0200 X-Google-Sender-Auth: ebb36fb88d6c6cee Message-ID: Subject: Re: Actions, tags, and the public timeline From: Vassil Dichev To: esme-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 > 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.