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 hirsch.dick@gmail.com
 designates 209.85.220.214 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=idq4NgicXx48di0MAH7GS/pfws3p+uBU7IvIdJsaGMlxpfrqj1N3w4eH+Z0T8LxAJx
         KICBa24m/YToB2Vx5yHHyb80OQkujrE5hJEsLABrmAphDMPyPMlVoR7pi+RnSxO1Q+8X
         hzdnPUmrzg+vX6e6R31ytTVZM2+v4sdpD1mLU=
MIME-Version: 1.0
In-Reply-To: <68f4a0e80912131430g3ccc1568pda53ad3baa42b870@mail.gmail.com>
References: <68f4a0e80912121817j32d9675j8f191abe97911c67@mail.gmail.com>
	 <fa2d9f450912122114r789421eg4f9980029ea1c786@mail.gmail.com>
	 <c7fc82820912122245j95c428bi28fa4bc6a86a9ed0@mail.gmail.com>
	 <fa2d9f450912130101w76ecabdfp101fd1daed01c293@mail.gmail.com>
	 <c7fc82820912130244p309188dx69f6534b2dc72c2b@mail.gmail.com>
	 <68f4a0e80912130840td5fe07ev6611a5994a3fd969@mail.gmail.com>
	 <68f4a0e80912131430g3ccc1568pda53ad3baa42b870@mail.gmail.com>
Date: Sun, 20 Dec 2009 12:59:13 +0100
Message-ID: <fa2d9f450912200359j2a5b0d9dy3662b24fb4102fdd@mail.gmail.com>
Subject: Re: SchedulerActor.scala and "Regularly scheduled message" in the API
	feed
From: Richard Hirsch <hirsch.dick@gmail.com>
To: esme-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

@Ethan can you close this tem in Jira?

D.

On Sun, Dec 13, 2009 at 11:30 PM, Ethan Jewett <esjewett@gmail.com> wrote:
> I created Jira issue 144
> (https://issues.apache.org/jira/browse/ESME-144) and submitted a patch
> to filter these messages out for the api2 endpoint. Please apply the
> patch when you have the chance and then I'll retest on Stax and close
> the issue.
>
> Thanks!
> Ethan
>
> On Sun, Dec 13, 2009 at 10:40 AM, Ethan Jewett <esjewett@gmail.com> wrote:
>> Ok, perfect, I will work on doing that. Does it make the most sense to
>> do this in each place the timeline is provided (Timeline, public
>> timeline, each API), or at a lower level?
>>
>> Ethan
>>
>> On Sun, Dec 13, 2009 at 4:44 AM, Vassil Dichev <vdichev@apache.org> wrote:
>>> Ethan,
>>>
>>> In API2, you can match for messages which have RegularReason and
>>> filter them out, if they are not necessary.
>>>
>>>
>>> On Sun, Dec 13, 2009 at 11:01 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
>>>>>For some reason this message doesn't show up in the timeline, but it does come through the API.
>>>>
>>>>> I've decided not to put
>>>>> these messages on the timeline, because it's annoying to have a
>>>>> message every couple of minutes with just the current date in them.
>>>>
>>>> Maybe you can add this same code / functionality to the API2 so that
>>>> it doesn't send the messages.
>>>>
>>>> D.
>>>>
>>>> On Sun, Dec 13, 2009 at 7:45 AM, Vassil Dichev <vdichev@apache.org> wrote:
>>>>>> vassil should know if it is deletable or not.....
>>>>>>
>>>>>> Do you want to blog about growl notifications now working?
>>>>>
>>>>> You can't delete this functionality, or regular actions will no longer
>>>>> work. This means Atom/RSS feeds will only be updated the first time
>>>>> the action is set.
>>>>>
>>>>> Also, if you really want the regular messages to appear on your
>>>>> timeline, you can set a rule to resend these. I've decided not to put
>>>>> these messages on the timeline, because it's annoying to have a
>>>>> message every couple of minutes with just the current date in them.
>>>>>
>>>>
>>>
>>
>