From: Konstantin Osipov <kostja.osipov@gmail.com> To: lvasiliev <lvasiliev@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 3/6] iproto: Add negotiation phase Date: Thu, 26 Mar 2020 15:16:53 +0300 [thread overview] Message-ID: <20200326121653.GA6796@atlas> (raw) In-Reply-To: <09a887d4-7459-683b-8a10-c3a0d27bc8c3@tarantool.org> * lvasiliev <lvasiliev@tarantool.org> [20/03/26 14:18]: > Now it does't look like a session control packet because auth packet will be > sent to server only if authentication is needed ("Authentication in > Tarantool is optional, if no authentication is performed, session user is > ‘guest’"). But, theoretically, it can be used. You can authenticate guest to guest, it will work. > In this case, the answer must be changed from ok/fail to the answer with > payload. > In my opinion the negotiation looks as: > - the client offers options for the session > - the server sends the resulting response with options (which may differ > from the requested) > - the client decides to work with such settings or disconnect > I think that negotiation phase can be used for flexible session setup in the > future (not only for errors) Cost of establishing a connection should be as low as possible. A sharded tarantool cluster has n^2 of them, and n can be very big - each cpu core is its own instance. 400 000 connections per cluster are not uncommon. -- Konstantin Osipov, Moscow, Russia
next prev parent reply other threads:[~2020-03-26 12:16 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-24 12:45 [Tarantool-patches] [PATCH 0/6] Extending error functionality Leonid Vasiliev 2020-03-24 12:45 ` [Tarantool-patches] [PATCH 1/6] error: Add a Lua backtrace to error Leonid Vasiliev 2020-04-05 22:14 ` Vladislav Shpilevoy 2020-04-08 13:56 ` Igor Munkin 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 2/6] error: Add the custom error type Leonid Vasiliev 2020-04-05 22:14 ` Vladislav Shpilevoy 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 3/6] iproto: Add negotiation phase Leonid Vasiliev 2020-03-24 20:02 ` Konstantin Osipov 2020-03-25 7:35 ` lvasiliev 2020-03-25 8:42 ` Konstantin Osipov 2020-03-25 10:56 ` Eugene Leonovich 2020-03-25 11:13 ` Konstantin Osipov 2020-03-26 11:37 ` lvasiliev 2020-03-26 11:18 ` lvasiliev 2020-03-26 12:16 ` Konstantin Osipov [this message] 2020-03-26 12:54 ` Kirill Yukhin 2020-03-26 13:19 ` Konstantin Osipov 2020-03-26 13:31 ` Konstantin Osipov 2020-03-26 21:13 ` Alexander Turenko 2020-03-26 21:53 ` Alexander Turenko 2020-03-27 8:28 ` Konstantin Osipov 2020-03-26 23:35 ` Alexander Turenko 2020-03-27 8:39 ` Konstantin Osipov 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 4/6] error: Add extended error transfer format Leonid Vasiliev 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 5/6] error: Add test for extended error Leonid Vasiliev 2020-03-24 12:46 ` [Tarantool-patches] [PATCH 6/6] error: Transmit an error through IPROTO_OK as object Leonid Vasiliev 2020-03-27 23:11 ` [Tarantool-patches] [PATCH 0/6] Extending error functionality lvasiliev 2020-03-28 13:54 ` Alexander Turenko 2020-03-30 10:48 ` lvasiliev 2020-04-01 15:35 ` Alexander Turenko
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=20200326121653.GA6796@atlas \ --to=kostja.osipov@gmail.com \ --cc=lvasiliev@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 3/6] iproto: Add negotiation phase' \ /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