RFC 6202 on Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP

rfc-editor@rfc-editor.org Wed, 06 April 2011 00:32 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C198B28C13D for <ietf-announce@core3.amsl.com>; Tue, 5 Apr 2011 17:32:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.096
X-Spam-Level:
X-Spam-Status: No, score=-102.096 tagged_above=-999 required=5 tests=[AWL=-0.419, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, USER_IN_WHITELIST=-100]
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 vbPiXanlVjeQ for <ietf-announce@core3.amsl.com>; Tue, 5 Apr 2011 17:32:40 -0700 (PDT)
Received: from rfc-editor.org (rfcpa.amsl.com [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id 034D428C149 for <ietf-announce@ietf.org>; Tue, 5 Apr 2011 17:32:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7A7D3E0772; Tue, 5 Apr 2011 17:33:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6202 on Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP
From: rfc-editor@rfc-editor.org
Message-Id: <20110406003357.7A7D3E0772@rfc-editor.org>
Date: Tue, 05 Apr 2011 17:33:57 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Apr 2011 00:32:41 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6202

        Title:      Known Issues and Best Practices 
                    for the Use of Long Polling 
                    and Streaming in Bidirectional HTTP 
        Author:     S. Loreto, P. Saint-Andre,
                    S. Salsano, G. Wilkins
        Status:     Informational
        Stream:     IETF
        Date:       April 2011
        Mailbox:    salvatore.loreto@ericsson.com, 
                    psaintan@cisco.com, 
                    stefano.salsano@uniroma2.it,  gregw@webtide.com
        Pages:      19
        Characters: 44724
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-loreto-http-bidirectional-07.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6202.txt

On today's Internet, the Hypertext Transfer Protocol (HTTP) is often
used (some would say abused) to enable asynchronous, "server-
initiated" communication from a server to a client as well as
communication from a client to a server.  This document describes
known issues and best practices related to such "bidirectional HTTP"
applications, focusing on the two most common mechanisms: HTTP long
polling and HTTP streaming.  This document is not an Internet 
Standards Track specification; it is published for informational 
purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC