incubator-esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Hirsch <hirsch.d...@gmail.com>
Subject Re: Actions, tags, and the public timeline
Date Fri, 30 Oct 2009 10:33:45 GMT
>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.

True.

> 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.

Having a tag that specifies what the action origin ("rss", "atom",
etc.)  is a great idea. I think we should use tags more often.

D.

On Fri, Oct 30, 2009 at 10:58 AM, Vassil Dichev <vdichev@apache.org> 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.
>

Mime
View raw message