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 3/4] session: introduce binary box.session.push
Date: Thu, 7 Jun 2018 15:53:52 +0300	[thread overview]
Message-ID: <20180607125352.GA30262@chai> (raw)
In-Reply-To: <6952c89275280b57a7d94b759234488b1a1cff20.1527886471.git.v.shpilevoy@tarantool.org>

Hi,

My code review for this patch is on branch
box-session-push-kostja.

What still needs to be done:

- convert push.test to box-tap
- add a second argument to box.session.push() - which is reply
  sync, and test that it works. If the sync is not provided,
  session sync should be used.

There is follow up work, once this part of the patch is done:

- investigate whether we can use kharon to get rid discard_input messages
- think about alternatives which would preserve sync in a Lua
  routine. Looks like using an upvalue would do
  https://www.lua.org/pil/27.3.3.html

As a side note, this patch could well be split into 3:
- tx_fiber_init() refactoring
- kharon, and push implementation
- fiber_sync() and connection-multiplexing-safe implementation of
  box.session.sync()
 
Thanks,

* Vladislav Shpilevoy <v.shpilevoy@tarantool.org> [18/06/02 02:09]:

> Closes #2677
> ---
>  src/box/iproto.cc          | 241 +++++++++++++++++++++++++++++++--------
>  src/box/iproto_constants.h |   3 +
>  src/box/lua/net_box.lua    | 104 ++++++++++++-----
>  src/box/xrow.c             |  12 ++
>  src/box/xrow.h             |  12 ++
>  src/fiber.h                |  14 ++-
>  test/box/net.box.result    |   8 +-
>  test/box/net.box.test.lua  |   8 +-
>  test/box/push.result       | 274 ++++++++++++++++++++++++++++++++++++++++++---
>  test/box/push.test.lua     | 148 ++++++++++++++++++++++--
>  10 files changed, 719 insertions(+), 105 deletions(-)
> 

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

  reply	other threads:[~2018-06-07 12:53 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   ` Konstantin Osipov [this message]
2018-06-07 17:02     ` [tarantool-patches] " 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
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=20180607125352.GA30262@chai \
    --to=kostja@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='[tarantool-patches] Re: [PATCH v3 3/4] session: introduce binary box.session.push' \
    /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