From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 875D32C1AB for ; Thu, 18 Apr 2019 11:19:30 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OT-bxImg3vkr for ; Thu, 18 Apr 2019 11:19:30 -0400 (EDT) Received: from smtp41.i.mail.ru (smtp41.i.mail.ru [94.100.177.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id 469152BC3C for ; Thu, 18 Apr 2019 11:19:30 -0400 (EDT) Received: by smtp41.i.mail.ru with esmtpa (envelope-from ) id 1hH8oy-0005ee-JM for tarantool-patches@freelists.org; Thu, 18 Apr 2019 18:19:28 +0300 Date: Thu, 18 Apr 2019 18:19:28 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH 3/4] swim: fix a bug with invalidation of round msg in fly Message-ID: <20190418151928.GE13022@chai> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: tarantool-patches-bounce@freelists.org Errors-to: tarantool-patches-bounce@freelists.org Reply-To: tarantool-patches@freelists.org List-Help: List-Unsubscribe: List-software: Ecartis version 1.0.0 List-Id: tarantool-patches List-Subscribe: List-Owner: List-post: List-Archive: To: tarantool-patches@freelists.org * Vladislav Shpilevoy [19/04/18 09:03]: Why have a concept of invalidation at all? Why can't you simply always keep the message up to date (built)? Don't you think member updates are so rare that you're winning very little by building on demand but the code is more complex because of it? The patch is OK to push. -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov