Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:130750 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 919021A00BC for ; Sun, 3 May 2026 12:01:07 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1777809672; bh=/Kdj4m6XWx+bVZKj/OQFmkvXSZF/OkL9vO2bxkj7uug=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Ajgda4uhquRaaS0Sfdr6gfMaLifiswDlbge9gFy6/6hOZfAMGrU+CCBw21G5nFylo YoN5lX5XRQ1vh9PrPurlqQKp8C98r+g/x9lTYg4OaIw373QcVEfifcvhVgvWx+5ZON Mo6+FAOsudH813XeWH3bIS2g/Co5q7FVM80SCsTVxa9TydO9DK2nPOagfRI6Ma7ZYp Q1sETIyGo4uUO0ms2czK4TcJpO40tXa1xOIQRiKSiRMxDvYLcbFJC2Bw+r/oem6S8G QRrGpNnVh1Fx6RA2U0/xbqgyN10ERgdYEmikRdMxMmxEjYZPQLk2dy7qEewiaLNrIJ 2fi16b67mUR3A== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5D78E180062 for ; Sun, 3 May 2026 12:01:11 +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, 3 May 2026 12:01:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bastelstu.be; s=mail20171119; t=1777809664; bh=jC5iM5bNzgDKoGHqclTVX9ofPXYcojRki8/CuCkZZsw=; h=MIME-Version:Date:From:To:Cc:Subject:In-Reply-To:References: Message-ID:Content-Type:from:to:cc:subject:message-id; b=Ew1wXPWZi7sUd1Jcupp3BhG4ordLIHzGKKVyAcwaZR5fj509ayzqjL/e4O5MSZw6Z NCgi2ww9jnisKHTQblYClS5TiSCFWCV7EShP+0aMWUpw8TC5HSeUozDl8c7cAVe+Zj nQ9dlAbef/IhLlnzzeaXSKIKsxIsucqSTlcxLKj1EDXCVrR4dhNlxV3wxyc1xTZdSV 1Q5YZScn4x8wVU6Nr9ar4mU5HNIvG/oHng/QNj32tqgqreqYViOblDMahEe1ARcymW dAlca/ku6R6iegp4xWbDYqs6SZc1RRI/BvNOesnuQEFyv8CTCTFWL1Y2FKqe+Jsn9X Tz7U8jVi/FckQ== Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Date: Sun, 03 May 2026 14:01:03 +0200 To: erictnorris@gmail.com Cc: PHP internals Subject: Re: [PHP-DEV] `COM_RESET_CONNECTION` support in `mysqlnd` In-Reply-To: References: <3ff59f9b3d7a872dc0159651848dace8@bastelstu.be> Message-ID: <46155eca0b1416f045856ef48be5c444@bastelstu.be> 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 Am 2026-04-30 16:11, schrieb Eric Norris: >> Somewhat relatedly, see: >> https://github.com/php/php-src/pull/21159#issuecomment-4111691063. I >> think it would be good to decide both cases at the same time, since >> they >> are reasonably similar. > > That could make sense, and how would you suggest we proceed to decide > the case? I'll admit that I'd be hesitant to need to resolve that via > an RFC, since if the RFC failed I'd need to potentially make another > RFC just for my change + some INI setting, and so it'd be quite some > time until I could get this merged. That's not to say we shouldn't do > it, I'm just noting my hesitation. A single RFC with two primary votes to independently resolve each of the two cases (at the same time) would work. Given the concerns and the similarity between both, I don't think we can do without an RFC. Best regards Tim Düsterhus