From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp47.i.mail.ru (smtp47.i.mail.ru [94.100.177.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id CEF9A469719 for ; Sat, 22 Feb 2020 17:47:43 +0300 (MSK) References: <20200221195140.GE68447@tarantool.org> <20200222083446.GF68447@tarantool.org> From: Vladislav Shpilevoy Message-ID: <3428db53-ad6b-ad05-de11-be0cf31dd139@tarantool.org> Date: Sat, 22 Feb 2020 15:47:41 +0100 MIME-Version: 1.0 In-Reply-To: <20200222083446.GF68447@tarantool.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Tarantool-patches] [PATCH 1/1] iproto: show real port in logs and box.info.listen List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sergey Ostanevich Cc: tarantool-patches@dev.tarantool.org On 22/02/2020 09:34, Sergey Ostanevich wrote: > Vlad, after thinking over the patch some more I've got a feeling it can > break backward compatibility. Can Tarantool with these changes in iproto > successfully communicate to the one without the changes? Why would it break anything? This has nothing to do with the protocol or network communication. This is just a new record in box.info table. I don't see how is it related to cross version interaction.