Tarantool development patches archive
 help / color / mirror / Atom feed
From: Konstantin Osipov <kostja@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@freelists.org
Subject: [tarantool-patches] Re: [PATCH v3 4/4] netbox: introduce iterable future objects
Date: Fri, 8 Jun 2018 06:52:24 +0300	[thread overview]
Message-ID: <20180608035224.GF6866@chai> (raw)
In-Reply-To: <9354d48e-78b5-9906-6f0c-057ce69b2389@tarantool.org>

* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [18/06/07 23:59]:
> On 07/06/2018 15:56, Konstantin Osipov wrote:
> > * Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [18/06/02 02:09]:
> > > Netbox has two major ways to execute a request: sync and async.
> > > During execution of any a server can send multiplie responses via
> > > IPROTO_CHUNK. And the execution ways differ in how to handle the
> > > chunks (called messages or pushes).
> > 
> > Please don't use asserts. They are hell to debug. Please use
> > tap suite if you need to check things, or simple output the result
> > you expect.
> 
> I have removed assertions and use output checking.
> 
> > 
> > The patch itself looks good to me. Did you send a message to
> > docbot about the new API?
> > 
> 
> Yes, I have already created docbot request. But I do not agree with
> the API, when push by default is taken from session.sync. If you want
> make the sync be optional, we must either
> 
> * make it mandatory, fix box.session.sync()/introduce fiber_sync()/something
>   else, then allow to omit sync;
> 
> Or
> 
> * fix sync and then commit box.session.push with optional sync. Or with no
>   sync, and allow it when somebody asks.

Vlad, thank you for voicing your disagreement. Please prepare a
patch which makes box.session.push() second argument optional.
Thanks.

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

  reply	other threads:[~2018-06-08  3:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 20:55 [tarantool-patches] [PATCH v3 0/4] box.session.push Vladislav Shpilevoy
2018-06-01 20:55 ` [tarantool-patches] [PATCH v3 1/4] session: introduce text box.session.push Vladislav Shpilevoy
2018-06-01 20:55 ` [tarantool-patches] [PATCH v3 2/4] session: enable box.session.push in local console Vladislav Shpilevoy
2018-06-01 20:55 ` [tarantool-patches] [PATCH v3 3/4] session: introduce binary box.session.push Vladislav Shpilevoy
2018-06-07 12:53   ` [tarantool-patches] " Konstantin Osipov
2018-06-07 17:02     ` Vladislav Shpilevoy
2018-06-08  3:51       ` Konstantin Osipov
2018-06-01 20:55 ` [tarantool-patches] [PATCH v3 4/4] netbox: introduce iterable future objects Vladislav Shpilevoy
2018-06-07 12:56   ` [tarantool-patches] " Konstantin Osipov
2018-06-07 17:02     ` Vladislav Shpilevoy
2018-06-08  3:52       ` Konstantin Osipov [this message]
2018-06-08 14:20         ` Vladislav Shpilevoy

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=20180608035224.GF6866@chai \
    --to=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='[tarantool-patches] Re: [PATCH v3 4/4] netbox: introduce iterable future objects' \
    /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