On Tue, Sep 20, 2011, at 06:44 PM, Sébastien Michel wrote:
> Hi all,
>
> progress is being made in the rewrite of our code toward the master branch.
> I pushed an update in our github repository, below the changelog :
>
> 1) adding the support of these event types:
> - MessageAppend
> - MessageExpire
We're looking to use the NEW and APPEND events to send notifications
to users including a link which can take them directly to the message.
To do this, we need to know what UID it was given - but looking at the
code we have this:
5f395e9c (Sébastien Michel 2012-08-08 17:33:39 +0200 331) static int
mboxevent_expected_param(enum event_type type, enum event_param pa
5f395e9c (Sébastien Michel 2012-08-08 17:33:39 +0200 332) {
[...]
5f395e9c (Sébastien Michel 2012-08-08 17:33:39 +0200 390) case
EVENT_UIDSET:
5f395e9c (Sébastien Michel 2012-08-08 17:33:39 +0200 391) if (type &
(EVENT_MESSAGE_NEW|EVENT_MESSAGE_APPEND))
5f395e9c (Sébastien Michel 2012-08-08 17:33:39 +0200 392) return 0;
5f395e9c (Sébastien Michel 2012-08-08 17:33:39 +0200 393) break;
Is there any reason why you don't return the uidset in _NEW or _APPEND?
The other place that might make sense is in the URI itself. What do you think?
Regards,
Bron.
--
Bron Gondwana
br...@fastmail.fm
