Return-Path: X-Original-To: apmail-hc-dev-archive@www.apache.org Delivered-To: apmail-hc-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 192A618683 for ; Mon, 1 Feb 2016 21:27:03 +0000 (UTC) Received: (qmail 95110 invoked by uid 500); 1 Feb 2016 21:27:03 -0000 Delivered-To: apmail-hc-dev-archive@hc.apache.org Received: (qmail 95076 invoked by uid 500); 1 Feb 2016 21:27:03 -0000 Mailing-List: contact dev-help@hc.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "HttpComponents Project" Delivered-To: mailing list dev@hc.apache.org Received: (qmail 95063 invoked by uid 99); 1 Feb 2016 21:27:02 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Feb 2016 21:27:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 41793C0873 for ; Mon, 1 Feb 2016 21:27:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 18K9VQnfIbFH for ; Mon, 1 Feb 2016 21:26:50 +0000 (UTC) Received: from mail-lb0-f181.google.com (mail-lb0-f181.google.com [209.85.217.181]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 2C96431ADD for ; Mon, 1 Feb 2016 21:26:50 +0000 (UTC) Received: by mail-lb0-f181.google.com with SMTP id cl12so82919864lbc.1 for ; Mon, 01 Feb 2016 13:26:50 -0800 (PST) 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; bh=KoHLBzu8NNad8bbK0B4WCO1z2kKzUxEQVQTeKsXUPwg=; b=gUyfhkwhwHYhPHGd8M9ZUdAWL+a0J82IqoC46e1o5mF5CiDt/DRO+6YsP4ET4r4Any 3LdUkK1VbX41x1+qoeW+7hJFzZZa6SKFsNKNfyGJf7TkZbWuojgJ8pUQzoox6bvz/fem 5AdcTyOTnBC+npM3YAbEP+QJ8258vHad18xMU5UaRMLDRpBF6S1wOm1btUHJufWyVllH 0d9YLp2RZhR4vejlbkrYCWuK+BYRkHrS7WVk7PUbDrENFwQQuym1ZvbNtt4ZbpIlHazP pNKFR3S1ipmzINlJm9HNaaxvjSwlsqg+MC1G8v+IwJ2g/LOEP6x5epXMjwrAZpxpHDXm 1NWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=KoHLBzu8NNad8bbK0B4WCO1z2kKzUxEQVQTeKsXUPwg=; b=GU/VfApE/CujtuA3HDzQp/z2Pcn3Nu3oRCwF1zU8+FcrUqQyn3DyzxRgqjEio19j1n mGxOVHi7MiPwDLDl3Afle+0OZKOucW52m8ra+2/crOYc/Xw3T3Ksy3kicwRFU1SllE/5 94AbBB/Yg+Sa1w/Yo0vFbC9EXXs1dvdgxwyDJbkiwIT1Uj5wfWBAlKvbvTYQ3TR+QVNM /JPL/YK0BvhFa95YpZhKr+N6WCq5orDbt0GO84O8NGOyXVdgRN6bedPI13lZKc9ElV28 Z354x8MtKk2gyhL0I357neeCItbKnPQ4DWh8DBiTFijONVnQxNpIfn6rch2FtwnKya+q vb1A== X-Gm-Message-State: AG10YORICVeit/KiA0B/GxPXVYoyJxWXBca5jTPbtXoYxSSmTFNQoIYQ4SHxzZj3Ep/0bnn3OgOMGay7vD0mpA== MIME-Version: 1.0 X-Received: by 10.112.135.39 with SMTP id pp7mr7588095lbb.43.1454362009613; Mon, 01 Feb 2016 13:26:49 -0800 (PST) Received: by 10.112.200.201 with HTTP; Mon, 1 Feb 2016 13:26:49 -0800 (PST) In-Reply-To: <1454359184.24550.11.camel@apache.org> References: <1454359184.24550.11.camel@apache.org> Date: Mon, 1 Feb 2016 13:26:49 -0800 Message-ID: Subject: Re: HTTP/2 naming convention From: Gary Gregory To: HttpComponents Project Content-Type: multipart/alternative; boundary=089e01228d1af53da3052abc0ab7 --089e01228d1af53da3052abc0ab7 Content-Type: text/plain; charset=UTF-8 On Mon, Feb 1, 2016 at 12:39 PM, Oleg Kalnichevski wrote: > On Mon, 2016-02-01 at 10:36 -0800, Gary Gregory wrote: > > Hi All: > > > > Cool to see HTTP/2 coming down the pike. > > > > I see a new module for HTTP2 and while I realize that this is fresh code, > > I'd like to talk about naming. > > > > I see types with the "H2" prefix, others with "Http2" and others with no > > prefix. > > > > I find the module name "httpcore5-h2" and "H2" in general not great. > > > > How about "http2core5" and a "Http2" prefix where we need one? > > > > I know there is virtually no risk of confusing HTTP code with the H2 > > database, but H2 does not say much to me. > > > > Thank you, > > Gary > > > > Hi Gary > > Actually according to the protocol spec "h2" is the standard protocol > identifier for HTTP/2. > > https://tools.ietf.org/html/rfc7540#section-3.1 > > I personally find "http2core5" terrible. I would rather have > "httpcore5-http2" instead if "httpcore5-h2" is deemed confusing. > I see, there is "h2" and "h2c"... well, I guess "httpcore5-h2" would work if the only thing in there is really just h2/h2c. Otherwise, "http2" is obvious and clear. Maybe "h2" will become better known as "oh, of course, this is HTTP/2" in the future? Pardon my newness to h2! :-) Gary > > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org > For additional commands, e-mail: dev-help@hc.apache.org > > -- E-Mail: garydgregory@gmail.com | ggregory@apache.org Java Persistence with Hibernate, Second Edition JUnit in Action, Second Edition Spring Batch in Action Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory --089e01228d1af53da3052abc0ab7--