Mailing-List: contact esme-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: esme-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of vdichev@gmail.com designates
 74.125.83.175 as permitted sender)
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=kTAMy1MDfKqHhPUQJgWg3O8m7UnaCP2naoXQ5B6zknvUBsGul7o+fYlHpG6Lphp4uC
         Z9/XLwWeJw/J2J57y1GC7CqHaS64OvDdNe4NsdJ4EHlzNrElDJgKavXEq0Ht6C6zeexb
         bqKteNrruXeVKqPADi6EtW+exSCXWBgSDNUls=
MIME-Version: 1.0
Sender: vdichev@gmail.com
In-Reply-To: <AANLkTilHGS5bP-6jG7iwv7blYbpU85JEgt6zK5nC32dv@mail.gmail.com>
References: <AANLkTilHGS5bP-6jG7iwv7blYbpU85JEgt6zK5nC32dv@mail.gmail.com>
Date: Fri, 4 Jun 2010 15:06:40 +0300
Message-ID: <AANLkTin8ddvqYwFY0SqIoqVZl3B3pdBXHNkznk1G-sKZ@mail.gmail.com>
Subject: Re: RSS feed for public timeline
From: Vassil Dichev <vdichev@apache.org>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I've been thinking for some time about some type of RSS/Atom feed (not
only for the public timeline), because this is one of the few ways you
can track which messages have already been read (apart from the mail
action, but it has a different usage scenario). So adding a feed for
e.g. all API methods that Twitter supports wouldn't be much more
effort than just for the public timeline. Of course, the feeds would
need authorization when necessary.

Vassil


On Fri, Jun 4, 2010 at 1:37 PM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
> I've been looking recently at various integration technologies and
> thought RSS might be one option for the public timeline. What about
> having a configuration setting, that a customer could decide whether
> it is active or not.
>
> We could probably re-use existing API code.
>
> D.
>