From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <v.shpilevoy@tarantool.org>
Received: from smtp29.i.mail.ru (smtp29.i.mail.ru [94.100.177.89])
 (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 A16E5452566
 for <tarantool-patches@dev.tarantool.org>;
 Sun, 17 Nov 2019 23:26:58 +0300 (MSK)
References: <746ed8a74c07907f85db8ec08e9d1937afc44f08.1573864467.git.v.shpilevoy@tarantool.org>
 <20191116130740.GF14490@atlas>
 <600a3a99-532c-7521-aa66-e96c11e76987@tarantool.org>
 <20191117174948.GC2498@atlas>
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Message-ID: <383aa58a-36e4-231a-44a4-f497a3a6a47e@tarantool.org>
Date: Sun, 17 Nov 2019 21:33:22 +0100
MIME-Version: 1.0
In-Reply-To: <20191117174948.GC2498@atlas>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [Tarantool-patches] [PATCH v2 1/1] iproto: don't destroy a
	session during disconnect
List-Id: Tarantool development patches <tarantool-patches.dev.tarantool.org>
List-Unsubscribe: <https://lists.tarantool.org/mailman/options/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=unsubscribe>
List-Archive: <https://lists.tarantool.org/pipermail/tarantool-patches/>
List-Post: <mailto:tarantool-patches@dev.tarantool.org>
List-Help: <mailto:tarantool-patches-request@dev.tarantool.org?subject=help>
List-Subscribe: <https://lists.tarantool.org/mailman/listinfo/tarantool-patches>, 
 <mailto:tarantool-patches-request@dev.tarantool.org?subject=subscribe>
To: Konstantin Osipov <kostja.osipov@gmail.com>, tarantool-patches@dev.tarantool.org

Ok, will do tomorrow. Kirill, please, don't push anything.

On 17/11/2019 18:49, Konstantin Osipov wrote:
> * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [19/11/17 20:44]:
>> But I could replace both flags with a 'state':
>> IPROTO_CON_ALIVE -> IPROTO_CON_CLOSED -> IPROTO_CON_PENDING_DESTROY,
>> IPROTO_CON_DESTROYED.
>>
>> Alive is an initial state. Closed is when the socket dies and
>> disconnect is sent to TX. Pending destroy is an optional state,
>> equivalent of do_destroy_on_close. Destroyed is an equivalent of
>> is_destroy_sent.
>>
>> If you think this is better, I can do that.
>>
> 
> I think it's better.
> 
>