Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BFC3D10AF6 for ; Mon, 24 Mar 2014 11:25:45 +0000 (UTC) Received: (qmail 59449 invoked by uid 500); 24 Mar 2014 11:25:44 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 59413 invoked by uid 500); 24 Mar 2014 11:25:43 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 59398 invoked by uid 99); 24 Mar 2014 11:25:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Mar 2014 11:25:43 +0000 Date: Mon, 24 Mar 2014 11:25:43 +0000 (UTC) From: "Sergey Beryozkin (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CXF-5638) Default WebSocket binding should optimize the metadata and optionally not write it MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944933#comment-13944933 ] Sergey Beryozkin edited comment on CXF-5638 at 3/24/14 11:24 AM: ----------------------------------------------------------------- The initial write over the web socket will include the metadata (status + headers) + data [1]. This can complicate it a bit for JavaScript clients. Proposal: if the JAX-RS method returns an OK response and it writes structured events into StreamingOuput then it may make sense to optimize and not write the metadata. This optimization can be enabled by the system or endpoint contextual property. To make this proposal working we should probably make a more compact representation of the metadata such that the client can read it all in one line and distinguish it from the other writes (though we can assume right now that the write without a starting line break is a metadata write) [1] https://cwiki.apache.org/confluence/display/CXF20DOC/WebSocket was (Author: sergey_beryozkin): The initial write over the web socket will include the metadata (status + headers) + data [1]. This can complicate it a bit for JavaScript clients. Proposal: if the JAX-RS method returns an OK response and it writes structured events into StreamingOuput then it may make sense to optimize and not write the metadata. This optimization can be enabled by the system or endpoint contextual property. [1] https://cwiki.apache.org/confluence/display/CXF20DOC/WebSocket > Default WebSocket binding should optimize the metadata and optionally not write it > ---------------------------------------------------------------------------------- > > Key: CXF-5638 > URL: https://issues.apache.org/jira/browse/CXF-5638 > Project: CXF > Issue Type: Improvement > Components: Transports > Reporter: Sergey Beryozkin > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.2#6252)