From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> To: tarantool-patches@dev.tarantool.org, kyukhin@tarantool.org Subject: [Tarantool-patches] [PATCH 1/1] session: deprecate box.session.push() 'sync' Date: Mon, 4 May 2020 23:43:41 +0200 [thread overview] Message-ID: <bd0c7652edec1fa695303ab06953556f2c86fe09.1588628598.git.v.shpilevoy@tarantool.org> (raw) box.session.push() has two parameters - data to push and 'sync'. The sync is a request ID with which the out of bound data should be pushed into a socket. This was introduced as a workaround for #3450, and is useless since its resolution. A user anyway can't push to different sessions, where that parameter could be useful. And pushing into requests of the same session, on the contrary, is something not really needed anywhere, not portable to non-binary session types (console, background), and is just dangerous since it is easy to add a bug here. The patch makes the parameter deprecated. Now on its usage there will be a rate limited warning in the logs. Part of #4689 --- Branch: http://github.com/tarantool/tarantool/tree/gerold103/gh-4689-push-sync-deprecate-2.4 Issue: https://github.com/tarantool/tarantool/issues/4689 The commit is for branch 2.4 only. src/box/lua/session.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/box/lua/session.c b/src/box/lua/session.c index 64453463a..d80e63ece 100644 --- a/src/box/lua/session.c +++ b/src/box/lua/session.c @@ -387,6 +387,8 @@ lbox_session_push(struct lua_State *L) sync = luaL_touint64(L, 2); if (sync != 0 || (lua_isnumber(L, 2) && lua_tonumber(L, 2) == 0)) { + say_warn_ratelimited("box.session.push() 'sync' " + "parameter is deprecated"); lua_pop(L, 1); break; } -- 2.21.1 (Apple Git-122.3)
next reply other threads:[~2020-05-04 21:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-04 21:43 Vladislav Shpilevoy [this message] 2020-05-18 8:45 ` Kirill Yukhin
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=bd0c7652edec1fa695303ab06953556f2c86fe09.1588628598.git.v.shpilevoy@tarantool.org \ --to=v.shpilevoy@tarantool.org \ --cc=kyukhin@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 1/1] session: deprecate box.session.push() '\''sync'\''' \ /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