Re: [Notifications] Use cases

Cullen Jennings <fluffy@cisco.com> Mon, 13 August 2007 22:39 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 1IKiZR-00045r-1j; Mon, 13 Aug 2007 18:39:33 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IKiZQ-00045l-61 for notifications-confirm+ok@megatron.ietf.org; Mon, 13 Aug 2007 18:39:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IKiZP-00045d-Sb for notifications@ietf.org; Mon, 13 Aug 2007 18:39:31 -0400
Received: from sj-iport-6.cisco.com ([171.71.176.117]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IKiZO-000883-Kb for notifications@ietf.org; Mon, 13 Aug 2007 18:39:31 -0400
Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 13 Aug 2007 15:39:30 -0700
X-IronPort-AV: i="4.19,256,1183359600"; d="scan'208"; a="199412365:sNHT47928483"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id l7DMdUwL030194; Mon, 13 Aug 2007 15:39:30 -0700
Received: from [192.168.4.177] (sjc-fluffy-vpn1.cisco.com [10.25.236.82]) by sj-core-1.cisco.com (8.12.10/8.12.6) with SMTP id l7DMdSF5027251; Mon, 13 Aug 2007 22:39:28 GMT
In-Reply-To: <953beacc0707301019l6170c84frff03cd14c8b39580@mail.gmail.com>
References: <4C38DC11F6B4FF4FAEA73E30DB5AA157D77DC3@esebe199.NOE.Nokia.com> <46AA4560.8040408@isode.com> <46AA4241.1060104@dcrocker.net> <953beacc0707301019l6170c84frff03cd14c8b39580@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <8377A826-8354-4784-B96F-A297AAAAB6AC@cisco.com>
Content-Transfer-Encoding: 7bit
From: Cullen Jennings <fluffy@cisco.com>
Subject: Re: [Notifications] Use cases
Date: Mon, 13 Aug 2007 15:38:11 -0700
To: Rohan Mahy <rohan.mahy@gmail.com>
X-Mailer: Apple Mail (2.752.3)
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1915; t=1187044770; x=1187908770; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=fluffy@cisco.com; z=From:=20Cullen=20Jennings=20<fluffy@cisco.com> |Subject:=20Re=3A=20[Notifications]=20Use=20cases |Sender:=20; bh=sMleAHPINjChdfclxRCjDhCWtwjiOE/95hpknX0ZLds=; b=tp05Ta5HJTKybCO4skdTQKu9GKedI+93JWX0cYEm2Aq1Jt6z0nEerPWG0mZLlzpu93LdQ3Iz JXNLIfWiXbcUXuMR3FzZ7UKECy7i5vsqN25bswigS1UXl9lUKsAyAjM4;
Authentication-Results: sj-dkim-3; header.From=fluffy@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; );
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: Rohan Mahy <rohan@ekabal.com>, 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

It seems like this use case was pretty much outside the email  
notifications scope we were trying to do for first version. Is this  
is the you have have to have it , or the could wait till later category?

On Jul 30, 2007, at 10:19 AM, Rohan Mahy wrote:

> 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


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