From: Konstantin Osipov <kostja@tarantool.org>
To: "Алексей Гаджиев" <alexey.gadzhiev@corp.mail.ru>
Cc: tarantool-patches@freelists.org,
Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Subject: [tarantool-patches] Re: Fwd: [PATCH 1/1] rfc: describe a Tarantool wire protocol
Date: Thu, 5 Apr 2018 13:03:27 +0300 [thread overview]
Message-ID: <20180405100327.GA15087@atlas> (raw)
In-Reply-To: <1522918872.186733999@f420.i.mail.ru>
* Алексей Гаджиев <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
prev parent reply other threads:[~2018-04-05 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 21:22 [tarantool-patches] " Vladislav Shpilevoy
2018-04-05 8:25 ` [tarantool-patches] " Konstantin Osipov
2018-04-09 15:31 ` [tarantool-patches] " Vladislav Shpilevoy
2018-06-28 11:45 ` [tarantool-patches] " Konstantin Osipov
[not found] ` <CAFoyxqh0QqNBVr7tuFF_uoUw-CvBKOVA3FCyWvixikberOxP9w@mail.gmail.com>
2018-04-05 9:01 ` [tarantool-patches] Re: Fwd: " Алексей Гаджиев
2018-04-05 9:37 ` Vladislav Shpilevoy
2018-04-05 10:03 ` Konstantin Osipov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180405100327.GA15087@atlas \
--to=kostja@tarantool.org \
--cc=alexey.gadzhiev@corp.mail.ru \
--cc=tarantool-patches@freelists.org \
--cc=v.shpilevoy@tarantool.org \
--subject='[tarantool-patches] Re: Fwd: [PATCH 1/1] rfc: describe a Tarantool wire protocol' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox