Re: [hybi] thewebsocketprotocol #28 (new): Fragmentation

"hybi issue tracker" <trac@tools.ietf.org> Mon, 22 November 2010 19:02 UTC

Return-Path: <trac@tools.ietf.org>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9BED3A6A3A for <hybi@core3.amsl.com>; Mon, 22 Nov 2010 11:02:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level:
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 7JJPtpTbJjGq for <hybi@core3.amsl.com>; Mon, 22 Nov 2010 11:02:35 -0800 (PST)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 514E63A69FB for <hybi@ietf.org>; Mon, 22 Nov 2010 11:02:35 -0800 (PST)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1PKbfm-0001dU-Rv; Mon, 22 Nov 2010 11:03:30 -0800
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: hybi issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: jat@google.com
X-Trac-Project: hybi
Date: Mon, 22 Nov 2010 19:03:30 -0000
X-URL: http://tools.ietf.org/hybi/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/hybi/trac/ticket/28#comment:1
Message-ID: <068.13890afeb438ea91112281cd06f0ea78@tools.ietf.org>
References: <059.5b3c3b280c1320a26d9c11c25e067e06@tools.ietf.org>
X-Trac-Ticket-ID: 28
In-Reply-To: <059.5b3c3b280c1320a26d9c11c25e067e06@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: jat@google.com, hybi@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: hybi@ietf.org
Subject: Re: [hybi] thewebsocketprotocol #28 (new): Fragmentation
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Nov 2010 19:02:36 -0000

#28: Fragmentation


Comment(by jat@…):

 I thought this was agreed in the discussions, though apparently not
 reflected in the draft.

 I believe we agreed that control messages could not be fragmented and
 could appear in the middle of a fragmented message (though "flattening"
 the opcode space so that control opcodes are intermixed with data opcodes
 makes it harder to specify that in a forward-compatible way).

-- 
----------------------------------+-----------------------------------------
 Reporter:  sm+ietf@…             |       Owner:     
     Type:  defect                |      Status:  new
 Priority:  major                 |   Milestone:     
Component:  thewebsocketprotocol  |     Version:     
 Severity:  -                     |    Keywords:     
----------------------------------+-----------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/hybi/trac/ticket/28#comment:1>
hybi <http://tools.ietf.org/hybi/>
The Hypertext-Bidirectional (HyBi) working group will seek
standardization of one approach to maintain bidirectional
communications between the HTTP client, server and intermediate
entities, which will provide more efficiency compared to the current
use of hanging requests.