Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of hirsch.dick@gmail.com
 designates 209.85.218.210 as permitted sender)
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=KTRQm1avtQAy02hvj0HkeIPPwNOC0dwuN62EidpYkCZfApQLvIt+78CjjaP410pvKT
         NeLqsIkAGq5jq0/n7xwLfIqhUNf55f3KaS1qRansUHESuwhrAyU7pbphISzQHmgvcACJ
         3m/vV7wqq2CUgx8HC1ObmGc/nY2HhkIH83s0Q=
MIME-Version: 1.0
In-Reply-To: <68f4a0e80911100641n7a7d2026g45ccd72dbc7a36e0@mail.gmail.com>
References: <68f4a0e80910270655g77db6321m53f8757a9ab115b2@mail.gmail.com>
	 <c7fc82820910270855h5b0fcd43t3f67123cdd1c014c@mail.gmail.com>
	 <68f4a0e80910290938x2614b4e6r5a4e05fa69f0ebb2@mail.gmail.com>
	 <fa2d9f450910291047s5f61f908x30e9e45b5359e405@mail.gmail.com>
	 <c7fc82820910300258s6e1d05w479fb6bae14b77ef@mail.gmail.com>
	 <68f4a0e80911100556q23fc9b37m68d7e3a056a3c078@mail.gmail.com>
	 <c7fc82820911100631w1f248b85u71021c894e679d86@mail.gmail.com>
	 <68f4a0e80911100641n7a7d2026g45ccd72dbc7a36e0@mail.gmail.com>
Date: Tue, 10 Nov 2009 15:48:38 +0100
Message-ID: <fa2d9f450911100648t54d46b01leea23076e9223b2e@mail.gmail.com>
Subject: Re: Actions, tags, and the public timeline
From: Richard Hirsch <hirsch.dick@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

>Can we send a message to more than one pool?

If I remember correctly a message can only be in one pool.  Based on
this restriction, it would only make sense to use the pool-linked
functionality for actions with messages that originate in non-pools
(for example, RSS feeds)

D.

On Tue, Nov 10, 2009 at 3:41 PM, Ethan Jewett <esjewett@gmail.com> wrote:
> I forgot about the way messages are handled when resending. I like
> newlines for adding pool and tag information to rss and atom actions.
>
> Everyone else agree that the "action" part of an action for atom or
> rss should look like this?:
>
> atom:http://the.address.com/to/my/feed.atom
> pool:My Pool
> tags:test,myfeed,address.com
>
> Can we send a message to more than one pool?
>
> Ethan
>
> On Tue, Nov 10, 2009 at 9:31 AM, Vassil Dichev <vdichev@apache.org> wrote:
>>> 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.
>>
>> For an atom/RSS feed I imagine it could be specified with something
>> like "pool:mypool" or "tags:tag1,tag2", separated by
>> newline/whitespace/commas from the action definition
>> "atom:http://server.org/whatever", depending on how we want to
>> separate several tags (spaces, commas).
>>
>> For resending messages this is problematic- messages are by design
>> immutable, so we can't add/edit tags (this has been discussed in the
>> past). Resending to another pool is also a security problem, as is
>> explicitly indicated in the last design specification by Bill
>> Fernandez.
>>
>> The important thing to remember is that a message is saved only
>> *once*. A user's timeline consists only of references to messages, not
>> of copies of messages. Thus there's a problem when you edit a message,
>> because this will affect all users with this message in the timeline.
>> This causes consistency problems on many levels, which could result in
>> confusion for the users, undefined behavior to streaming clients when
>> an old message is edited, and severe performance problems.
>>
>> So in short, for Atom/RSS the answer is easy, for resending I don't
>> believe it will be implemented.
>>
>> Vassil
>>
>