From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <tarantool-patches-bounce@freelists.org>
Received: from localhost (localhost [127.0.0.1])
	by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 212202A85F
	for <tarantool-patches@freelists.org>; Thu,  5 Apr 2018 06:03:32 -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 pu_iUl3WL-Vy for <tarantool-patches@freelists.org>;
	Thu,  5 Apr 2018 06:03:32 -0400 (EDT)
Received: from smtp20.mail.ru (smtp20.mail.ru [94.100.179.251])
	(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 CEDD02A3EA
	for <tarantool-patches@freelists.org>; Thu,  5 Apr 2018 06:03:31 -0400 (EDT)
Date: Thu, 5 Apr 2018 13:03:27 +0300
From: Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: Fwd: [PATCH 1/1] rfc: describe a Tarantool wire protocol
Message-ID: <20180405100327.GA15087@atlas>
References: <5ad2e4261e5ee48c84fecad13a32c8f9f38aeff0.1522876737.git.v.shpilevoy@tarantool.org>
 <CAFoyxqh0QqNBVr7tuFF_uoUw-CvBKOVA3FCyWvixikberOxP9w@mail.gmail.com>
 <1522918872.186733999@f420.i.mail.ru>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1522918872.186733999@f420.i.mail.ru>
Sender: tarantool-patches-bounce@freelists.org
Errors-to: tarantool-patches-bounce@freelists.org
Reply-To: tarantool-patches@freelists.org
List-help: <mailto:ecartis@freelists.org?Subject=help>
List-unsubscribe: <tarantool-patches-request@freelists.org?Subject=unsubscribe>
List-software: Ecartis version 1.0.0
List-Id: tarantool-patches <tarantool-patches.freelists.org>
List-subscribe: <tarantool-patches-request@freelists.org?Subject=subscribe>
List-owner: <mailto:>
List-post: <mailto:tarantool-patches@freelists.org>
List-archive: <http://www.freelists.org/archives/tarantool-patches>
To: =?utf-8?B?0JDQu9C10LrRgdC10Lkg0JPQsNC00LbQuNC10LI=?= <alexey.gadzhiev@corp.mail.ru>
Cc: tarantool-patches@freelists.org, Vladislav Shpilevoy <v.shpilevoy@tarantool.org>

* Алексей Гаджиев <alexey.gadzhiev@corp.mail.ru> [18/04/05 12:05]:
> Looks cool! Now we can send chunked data!
> 
> I have one question:
> Is IPROTO_OK mandatory packet in the response messages sequence?
> How can I detect if next push/result_set available if previous consists only of one chunk without   SQL_INFO_HAS_NEXT_CHUNK?
> 

Generally, you can't. The server doesn't know it yet itself. For
example, imagine this:

while (condition)
    box.session.push()
end
return;

In this case there can be variable number of pushes. 

But you know for sure there will be next packet before the
sequence of packets for this request ends - either CHUNK or OK.

-- 
Konstantin Osipov, Moscow, Russia, +7 903 626 22 32
http://tarantool.io - www.twitter.com/kostja_osipov