Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C2D159A7F for ; Thu, 5 Jul 2012 12:25:46 +0000 (UTC) Received: (qmail 47811 invoked by uid 500); 5 Jul 2012 12:25:43 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 47631 invoked by uid 500); 5 Jul 2012 12:25:41 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 47565 invoked by uid 99); 5 Jul 2012 12:25:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 12:25:38 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of knst.kolinko@gmail.com designates 209.85.220.173 as permitted sender) Received: from [209.85.220.173] (HELO mail-vc0-f173.google.com) (209.85.220.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Jul 2012 12:25:31 +0000 Received: by vcbfo13 with SMTP id fo13so7226704vcb.18 for ; Thu, 05 Jul 2012 05:25:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=VzSv+t2c85uK2AbBlVKCSWvRYdA8SAT1PHyNKIlbsoI=; b=zd3TBNHAYs8CTN/TXajfrhQM+bzIlmDlP7QPfPgwnCDF3aTvnnytfWeozP9S0b5RF5 v9pNfljaVj5cu0qDQFhIT4FbgQTGx1TeeWq7EDPFj4GZgvRteVIFKAXJU+v46AAf6YRA 8l+5d0ue9PK4gjjzUmK8Ax6p/exE98jHuLWinYU8DJf9anxwa4xfWj8NFxD8vSUm7eZs Qt3Gk+z5FTFF+8x4WeWfB9EF3MSEABgaOHwFJPeyW4KePpmqdB6ASRAGXtkyC1OscpBC o9AsTfdjSF0f9+u0su5+8hCzoh76pd6RD6PwXhY5hZQtI6GrEVpxYNrfkUdb/fYAxvCf lqDA== MIME-Version: 1.0 Received: by 10.220.223.201 with SMTP id il9mr7148259vcb.61.1341491110660; Thu, 05 Jul 2012 05:25:10 -0700 (PDT) Received: by 10.220.6.2 with HTTP; Thu, 5 Jul 2012 05:25:10 -0700 (PDT) In-Reply-To: <1341468742.24183.YahooMailNeo@web122306.mail.ne1.yahoo.com> References: <1341468742.24183.YahooMailNeo@web122306.mail.ne1.yahoo.com> Date: Thu, 5 Jul 2012 16:25:10 +0400 Message-ID: Subject: Re: Tomcat 7 and JIoEndpoint as used in ssl From: Konstantin Kolinko To: Tomcat Users List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 2012/7/5 Hermes Flying : > Hi, > > I have build a custom SSL implementation and I use that for the SSL conne= ctivity in Tomcat. > This was build back in Tomcat 5 and it works in Tomcat 6 > But now that we are trying to migrate in Tomcat 7 a change has been done = that breaks my implementation. > Specifically the org.apache.tomcat.util.netSSLImplementation#getServerSoc= ketFactory() has been changed to > > org.apache.tomcat.util.netSSLImplementation#getServerSocketFactory(Abstra= ctEndpoint endpoint) > at least this is a first difference I found so far. > > My question is: What is the need/use of this change? http://svn.apache.org/viewvc?view=3Drevision&revision=3D1044058 > In the previous version (with no params) my implementation handled everyt= hing. Am I supposed to do something with the AbstractEndpoint endpoint? I s= ee that this normally is JIoEndpoint. Am I supposed to pass some informatio= n back to it? Or has this been done just in case someone would need to do t= hat. org.apache.tomcat.util.net.jsse.JSSEImplementation extends SSLImplementatio= n { (...) @Override public ServerSocketFactory getServerSocketFactory(AbstractEndpoint endpoint) { return new JSSESocketFactory(endpoint); } } and JSSESocketFactory uses endpoint a lot. > What is the functionality of JIoEndpoint? The same as of AbstractEndpoint plus a bit more. Endpoint 1. represents the "server socket", on which Tomcat connector listens. 2. is responsible for socket management regardless of protocol (HTTP, AJP), especially the "server socket" management. 3. naturally serves as the storage for certain set of configurations options (the ones that are protocol-agnostic and ones that relate to socket management). Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org