Re: [Notifications] Reliability

Leif Johansson <leifj@it.su.se> Thu, 09 August 2007 09:19 UTC

Return-path: <notifications-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJ4BJ-000216-DL; Thu, 09 Aug 2007 05:19:49 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IJ4BI-000210-C8 for notifications-confirm+ok@megatron.ietf.org; Thu, 09 Aug 2007 05:19:48 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IJ4BH-00020s-Bi for notifications@ietf.org; Thu, 09 Aug 2007 05:19:47 -0400
Received: from smtp3.su.se ([130.237.93.228]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IJ4BH-0006OI-1R for notifications@ietf.org; Thu, 09 Aug 2007 05:19:47 -0400
Received: from localhost (localhost [127.0.0.1]) by smtp3.su.se (Postfix) with ESMTP id B64AE3BF3B; Thu, 9 Aug 2007 11:19:45 +0200 (CEST)
Received: from smtp3.su.se ([127.0.0.1]) by localhost (smtp3.su.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 22438-01-90; Thu, 9 Aug 2007 11:19:45 +0200 (CEST)
Received: from [10.0.0.11] (ua-83-227-179-169.cust.bredbandsbolaget.se [83.227.179.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.su.se (Postfix) with ESMTP id 5495D3BEDA; Thu, 9 Aug 2007 11:19:45 +0200 (CEST)
Message-ID: <46BADC44.2060706@it.su.se>
Date: Thu, 09 Aug 2007 11:20:04 +0200
From: Leif Johansson <leifj@it.su.se>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Zoltan.Ordogh@nokia.com
Subject: Re: [Notifications] Reliability
References: <4C38DC11F6B4FF4FAEA73E30DB5AA157E3F135@esebe199.NOE.Nokia.com>
In-Reply-To: <4C38DC11F6B4FF4FAEA73E30DB5AA157E3F135@esebe199.NOE.Nokia.com>
X-Enigmail-Version: 0.94.2.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at smtp.su.se
X-Spam-Status: No, hits=-2.279 tagged_above=-99 required=7 tests=[AWL=0.033, BAYES_00=-2.312]
X-Spam-Level:
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d6b246023072368de71562c0ab503126
Cc: notifications@ietf.org
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Message Notifications interest group discussion list <notifications.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/notifications>
List-Post: <mailto:notifications@ietf.org>
List-Help: <mailto:notifications-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=subscribe>
Errors-To: notifications-bounces@ietf.org

Zoltan.Ordogh@nokia.com wrote:
>
> Hi all,
> We have briefly touched the reliability issue during the BoF, but we
> did not actually go trhough with it.
> If this notification is not going to be reliable, what's the use for
> it? I mean:
> You have a new mail, but You don't get a notification - what the use
> of the whole framework then?
> Any thoughts on this?
> Thank You.
>
Well if you typically get email regularly and the purpose of the
notification mechanism is to notify you that you _may_ have
new mail then it won't matter much (imho) if you loose a
notify message now and again.

    Cheers Leif



_______________________________________________
Notifications mailing list
Notifications@ietf.org
https://www1.ietf.org/mailman/listinfo/notifications