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 D4CF12A51C for ; Wed, 10 Apr 2019 14:11:54 -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 Dsnq_mFvxSEd for ; Wed, 10 Apr 2019 14:11:54 -0400 (EDT) Received: from smtp50.i.mail.ru (smtp50.i.mail.ru [94.100.177.110]) (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 8D44729F2C for ; Wed, 10 Apr 2019 14:11:54 -0400 (EDT) Date: Wed, 10 Apr 2019 21:11:51 +0300 From: Konstantin Osipov Subject: [tarantool-patches] Re: [PATCH 0/2] swim broadcast Message-ID: <20190410181151.GM8268@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: Vladislav Shpilevoy Cc: tarantool-patches@freelists.org * Vladislav Shpilevoy [19/04/10 21:01]: > The patchset introduces broadcast tasks and API to broadcast pings. A ping > broadcast is useful when a cluster is just started, but UUIDs and URIs aren't > known in advance. Why do you need to send a broadcast message across multiple interfaces? Why not demand an interface name in the api? -- Konstantin Osipov, Moscow, Russia, +7 903 626 22 32 http://tarantool.io - www.twitter.com/kostja_osipov