esme-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ethan Jewett <esjew...@gmail.com>
Subject Re: A few requests and few bugs
Date Tue, 13 Apr 2010 14:00:53 GMT
Just that there are "reply-to message IDs" and "conversation IDs". The
action could fire depending on either one.

Ethan

On Tue, Apr 13, 2010 at 9:48 AM, Richard Hirsch <hirsch.dick@gmail.com> wrote:
> On Tue, Apr 13, 2010 at 3:40 PM, Ethan Jewett <esjewett@gmail.com> wrote:
>
>> On Tue, Apr 13, 2010 at 9:13 AM, Richard Hirsch <hirsch.dick@gmail.com>
>> wrote:
>> >
>> > But we've used actions with tag-based tests in the same way.  For
>> example,
>> > in the akibot and 12sprints integrations.
>>
>> After reading the Jira ticket it makes more sense to me. I took this
>> as asking for an action that waits for a particular message and then
>> does something. But you are actually asking for an action that waits
>> for *replies* to particular messages and does something.
>>
>> What I'm wondering now is whether we want to test on the message being
>> replied to or the conversation associated with the message. What do
>> you think? I'm thinking that the conversation makes more sense,
>> because it will catch replies to replies, for example.
>>
>
> Do you mean: The action is fired when messages are added to the conversation
> based on the message with the message_id named in the action test.
>
>
>>
>> Depending on what the developers are trying to accomplish, there may
>> also be ways to use the API to do this.
>>
>> Ethan
>>
>

Mime
View raw message