Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 76719 invoked from network); 11 Nov 2010 23:02:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Nov 2010 23:02:42 -0000 Received: (qmail 81516 invoked by uid 500); 11 Nov 2010 23:03:13 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 81465 invoked by uid 500); 11 Nov 2010 23:03:13 -0000 Mailing-List: contact dev-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 dev@cxf.apache.org Received: (qmail 81457 invoked by uid 99); 11 Nov 2010 23:03:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Nov 2010 23:03:13 +0000 X-ASF-Spam-Status: No, hits=-1.9 required=10.0 tests=HTML_MESSAGE,MIME_QP_LONG_LINE,RCVD_IN_DNSWL_HI,RCVD_NUMERIC_HELO,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of iclin@cisco.com designates 64.102.122.148 as permitted sender) Received: from [64.102.122.148] (HELO rtp-iport-1.cisco.com) (64.102.122.148) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 11 Nov 2010 23:03:01 +0000 Authentication-Results: rtp-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuAIAC8F3EytJV2a/2dsb2JhbACBcZJejSpQAnGmTZsighWCLIEJBIRahX6DEYRr X-IronPort-AV: E=Sophos;i="4.59,185,1288569600"; d="scan'208,217";a="181003910" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rtp-iport-1.cisco.com with ESMTP; 11 Nov 2010 23:02:40 +0000 Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id oABN2ew2015525 for ; Thu, 11 Nov 2010 23:02:40 GMT Received: from xmb-rcd-110.cisco.com ([72.163.62.152]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 11 Nov 2010 17:02:40 -0600 Received: from 171.69.152.187 ([171.69.152.187]) by XMB-RCD-110.cisco.com ([72.163.62.152]) with Microsoft Exchange Server HTTP-DAV ; Thu, 11 Nov 2010 23:02:40 +0000 User-Agent: Microsoft-Entourage/12.27.0.100910 Date: Thu, 11 Nov 2010 15:02:39 -0800 Subject: What is back-channel in Destination.getBackChannel()? From: iclin To: Message-ID: Thread-Topic: What is back-channel in Destination.getBackChannel()? Thread-Index: AcuB9ImOVfkxCuT5yk2oCIv37pN3dA== Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3372332559_9569544" X-OriginalArrivalTime: 11 Nov 2010 23:02:40.0413 (UTC) FILETIME=[8A65ECD0:01CB81F4] X-Virus-Checked: Checked by ClamAV on apache.org --B_3372332559_9569544 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Hi, I'm trying to implement a customize org.apache.cxf.transport.Destination by extending AbstractDestination. In the=A0Destination=A0interface there is a method called getBackChannel() and the description reads like: "Retreive a back-channel=A0Conduit, which must be policy-compatible with the current Message and associated Destination. For example compatible Quality of Protection must be asserted on the back-channel" I still do not understand what is the purpose of a 'back-channel' and when it is used to properly implement my Destination. A more elaborated description will be very helpful. Thanks. --B_3372332559_9569544--