From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: tarantool-patches@freelists.org,
Konstantin Osipov <kostja@tarantool.org>
Subject: [tarantool-patches] Re: [PATCH 1/1] rfc: describe proxy
Date: Fri, 6 Apr 2018 13:21:34 +0300 [thread overview]
Message-ID: <c4ba0983-48fe-28d9-e710-a580b164b652@tarantool.org> (raw)
In-Reply-To: <20180405202353.GD3953@atlas>
> What happens if the data changes after the client has connected?
> then you get all the shortcomings of the rejected proposals.
> In a nutshell, this proposal is not different from tracking
> schema_version and re-fetching the schema when it changes, but
> more pessimistic in nature.
Tarantool do not disconnect already connected clients, if their
credentials were changed. So
there is no problem for existing clients. We must check passwords for
new ones only.
prev parent reply other threads:[~2018-04-06 10:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180327110504.GA26560@atlas>
2018-04-05 14:23 ` [tarantool-patches] " Vladislav Shpilevoy
2018-04-05 20:23 ` [tarantool-patches] " Konstantin Osipov
2018-04-06 10:20 ` [tarantool-patches] " Vladislav Shpilevoy
2018-04-06 10:21 ` Vladislav Shpilevoy [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=c4ba0983-48fe-28d9-e710-a580b164b652@tarantool.org \
--to=v.shpilevoy@tarantool.org \
--cc=kostja@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='[tarantool-patches] Re: [PATCH 1/1] rfc: describe proxy' \
/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