Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:130214 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id E405A1A00BC for ; Sun, 1 Mar 2026 20:05:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1772395536; bh=716shIT6Jx/732dyIktjmsEdzpE9PzSijQIYy8msr2A=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=MY5HS6Sc8ovHidTWgP34mCalBuKO5p3D2xAwfkems4TW6QxXGQsH59afvDf+OwR1j ND6vcNaRrSGhSheg/vQ58u+MZ31KEQ/rPIUDP3gPpVtPiDQF1KkTgC0/uk3VLsNQOd N6TT/uX9t5U49IWbYC2FK68Bnh+zzuEhoasvqRxX7k3zWF3qHYpQg8fwvG0LezZClq lDvZi+VVe7dNSp9wt6HVOQoAJQpf+PdtGoSmjxbLa+W3A+/kcKucytnogwbsYouMZr 9AqlOE6rADSnSfCu+xjKXhqd9o8/W4+JbXSapKohr6P+3esPiPrtmthEWWtbH7NDtT 5nhW7TnlLjZkQ== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id EAC1118007E for ; Sun, 1 Mar 2026 20:05:35 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from chrono.xqk7.com (chrono.xqk7.com [176.9.45.72]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 1 Mar 2026 20:05:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1772395524; bh=6AxBbawgPKBYm5Tacbb83zseeEESjVEZpRL2UukK3dg=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type:from:to:cc:subject:message-id; b=WxaAA3pGE0+R9MB5QRF8MhVHmhOM++n6w8ONnARYYzdEh03vOoysYx22no9JyjAUa b9XbhdZy0ItFsF3KG4RgrBWNlRArybQglTCEw7HjaqhKHHw2dphBRUJ2uDIYpIMnKa NJJBW5831/HP9C/Ylji7+Z1jWznS9dcI0mFM9WHw1hlE+KQM2/HmcGh8zhhvLeWUEK PfOer0qXda06eLjGGKTsNRH6+G8rC7gPKzQRkccakMdvRruFPnWGQiFVaPkUlaMVUU GnK5meq/lQmt/Q+u0it11ZRoP5Vh8TDlXUz1dgjbnlpjec8lq4aLUwcLS3RcLWFOam ZI33kiYbv1dZg== Message-ID: Date: Sun, 1 Mar 2026 21:05:22 +0100 Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Subject: Re: [PHP-DEV] [RFC] TLS Session Resumption Support for Streams To: Jakub Zelenka Cc: PHP internals list References: <2d741c45-9c92-4404-a0d5-02bf26a557b1@bastelstu.be> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit From: tim@bastelstu.be (=?UTF-8?Q?Tim_D=C3=BCsterhus?=) Hi On 3/1/26 20:48, Jakub Zelenka wrote: > The policy recommends consistency with existing symbols and there are > already OpenSSLCertificate, OpenSSLCertificateSigningRequest and > OpenSSLAsymmetricKey. So I think we should stick with no namespace here and > calls it OpenSSLSession and OpenSSLException. I will introduce that > exception as I agree it makes more sense. The policy also states: > This is a somewhat loose guideline, and applies more strongly to functions than classes. I don't feel strongly about the OpenSSLSession class, but I feel strongly about the exception hierarchy: It should immediately be introduced into the namespace, because the exception hierarchy is relevant to the entire extension (e.g. also to newly namespaced bits) and namespacing it later will become messy. However since the OpenSSLSession class will also be an entirely new API with proper methods instead of just an opaque resource object, it is more likely to be directly used by developers. So putting it into a namespace to follow the “latest best practices” there still makes sense to me, even if it introduces some inconsistency. You always need to start with *something*, otherwise you're never going to to the migration for existing extensions. Best regards Tim Düsterhus