[Bug 13349] Undraft mail notification spec

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=13349

--- Comment #44 from Will Thompson <will.thompson at collabora.co.uk> 2010-10-21 07:19:32 PDT ---
(In reply to comment #41)
> (In reply to comment #40)
> > Undraft is blocked. On Bug #24901, wjt writes:
> > > One possible roadblock for re-using MailNotification [for voicemail
> > > as per Bug #24901]: GSM voicemail
> > > notifications need to be acked to the network. Maybe we could get away with
> > > Ring just acking them immediately, and caching them on disk, or something.
> From my point of view the voicemail is orthogonal to IM mail notification. The
> mail notification is lightweight notification, you have no guaranty to get them
> all and you usually have no mean to consult them all.

I misunderstood: you don't have to ack GSM voicemail notifications.

> > > Also: Rob wondered whether mail notification should be a singleton channel, to
> > > ensure that it's dispatched. Either that, or we need connection-observing API
> > > as Guillaume requests in bug 28974.
> I don't agree, it's completely pointless to ensure notification dispatching.
> The way it works is very simple, read the state and stay inform. There exist no
> server that will resend notification or keep them offline until you are online.
> This would be a total waste of server resources.

True. Indeed GSM behaves like that: you only get the notification once, and you
have to cache it locally if you want to save it.

So actually, this interface could be used for voicemail notifications without
modification, only the addition of new keys.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.