Re: [Notifications] Use cases
"Eric Burger" <eburger@bea.com> Tue, 31 July 2007 10:42 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 1IFpAv-0002Mq-7U; Tue, 31 Jul 2007 06:42:01 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IFpAt-0002Fy-Pk for notifications-confirm+ok@megatron.ietf.org; Tue, 31 Jul 2007 06:42:00 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IFpAq-00020m-3Z for notifications@ietf.org; Tue, 31 Jul 2007 06:41:56 -0400
Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IFpAp-00031m-Gl for notifications@ietf.org; Tue, 31 Jul 2007 06:41:56 -0400
Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l6VAfqXx008841; Tue, 31 Jul 2007 03:41:52 -0700
Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l6VAfofc000741; Tue, 31 Jul 2007 03:41:51 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Subject: Re: [Notifications] Use cases
Date: Tue, 31 Jul 2007 03:41:49 -0700
Message-ID: <A5E9CBACB726CB4BAA3DAFF0925C188F129A76@repbex01.amer.bea.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Notifications] Use cases
Thread-Index: AcfSzehpsShTA9FmTUq3XvHfHPsxNgAkX2mB
From: Eric Burger <eburger@bea.com>
To: rohan.mahy@gmail.com, notifications@ietf.org
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc:
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
First scenario: is that not what sieve does today? Second scenario: once you assume a long-lived TCP connection, the IMAP connection is free. I would also offer the IMAP NOTIFY message can be an order of magnitude smaller than a fully-routed SIP message, which would save bandwidth. -- Sent from my wireless e-mail device. Sorry if terse. We all need lemonade: see <http://www.standardstrack.com/ietf/lemonade> for what lemonade is. -----Original Message----- From: Rohan Mahy <rohan.mahy@gmail.com> To: notifications@ietf.org <notifications@ietf.org> CC: Rohan Mahy <rohan@ekabal.com> Sent: Mon Jul 30 10:19:57 2007 Subject: Re: [Notifications] Use cases Scenario: A widget on my cell phone that correlates all package tracking emails from Federal Express. It is interested in the Subject and To header of all emails sent From tracker.fedex.com. When it gets a new notification, it parses the tracking number from the Subject and does an HTTP fetch to get the current status of the package. It can then beep or chime or prompt you to send an email or a phone call or SMS when various things happen (package picked up, package delivered, package delayed, package cleared customs). This model would apply nicely to other widgets for package tracking, flight status, sales order notifications, and stock trade confirmations. Problem: The cell phone does not want to poll for new messages (for example using IMAP) because this would negatively affect battery life. Better to use an existing open TCP connection already used by SIP or XMPP to receive these async notifications. Also, the phone is only interested in a filtered view of notifications. There are ways of doing this today in email, but just forwarding all your email to an IM gateway using a static filter isn't sufficient. If the phone has multiple widgets, these filters my need to be somewhat dynamic. Market: Widgets like this are popping up left and right, but they use HTTP polling. The market would like these apps and decent battery consumption too. thanks, -rohan _______________________________________________ Notifications mailing list Notifications@ietf.org https://www1.ietf.org/mailman/listinfo/notifications Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. _______________________________________________ Notifications mailing list Notifications@ietf.org https://www1.ietf.org/mailman/listinfo/notifications
- Re: [Notifications] Use cases Tony Hansen
- [Notifications] Use cases Zoltan.Ordogh
- Re: [Notifications] Use cases Alexey Melnikov
- RE: [Notifications] Use cases Zoltan.Ordogh
- Re: [Notifications] Use cases Dave Crocker
- RE: [Notifications] Use cases Zoltan.Ordogh
- Re: [Notifications] Use cases Rohan Mahy
- Re: [Notifications] Use cases Eric Burger
- Re: [Notifications] Use cases Dave Crocker
- Re: [Notifications] Use cases Cullen Jennings
- Re: [Notifications] Use cases Leif Johansson
- Re: [Notifications] Use cases Cullen Jennings
- Re: [Notifications] Use cases Leif Johansson
- Re: [Notifications] Use cases Cullen Jennings