[OAUTH-WG] Issue: 3.5.3 Polling?
Eliot Lear <lear@cisco.com> Mon, 19 April 2010 13:09 UTC
Return-Path: <lear@cisco.com>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BF01A3A6ABA for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 06:09:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.152
X-Spam-Level:
X-Spam-Status: No, score=-8.152 tagged_above=-999 required=5 tests=[AWL=2.446, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPwS-Z08VnMe for <oauth@core3.amsl.com>; Mon, 19 Apr 2010 06:09:52 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 841DC3A6A97 for <oauth@ietf.org>; Mon, 19 Apr 2010 06:09:51 -0700 (PDT)
Authentication-Results: ams-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArUBAELzy0uQ/uCWiWdsb2JhbACDFJhiFQEBAQoLEREGHKBjiGGQRIQibgQ
X-IronPort-AV: E=Sophos; i="4.52,235,1270425600"; d="scan'208,217"; a="59632872"
Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 19 Apr 2010 13:09:42 +0000
Received: from elear-mac.local (ams3-vpn-dhcp5455.cisco.com [10.61.85.78]) by ams-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id o3JD9frG005252 for <oauth@ietf.org>; Mon, 19 Apr 2010 13:09:42 GMT
Message-ID: <4BCC5610.8000607@cisco.com>
Date: Mon, 19 Apr 2010 15:09:36 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.5pre) Gecko/20100417 Lanikai/3.1b2pre
MIME-Version: 1.0
To: OAuth WG <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="------------080908090309060401020701"
Subject: [OAUTH-WG] Issue: 3.5.3 Polling?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Apr 2010 13:09:52 -0000
For this section I would like to understand the logic of using polling rather than a client blocking. I could imagine several legitimate reasons, but the text isn't there, and I have a very vivid (and sometimes wrong) imagination. Eliot
- [OAUTH-WG] Issue: 3.5.3 Polling? Eliot Lear