Thank your information very much! Thanks, Ken Cheng
On Fri, Apr 26, 2019 at 12:32 AM Igor Sapego <isap...@apache.org> wrote: > The point of "Best effort" is that we do not guarantee every requested > to be routed to the optimal node, we only apply our best effort to make > this happen. > > No, cluster will NOT return a address list to the client upon handshake > because. > > 1. It may be not secure to connect to nodes, which user did not specified > in the connection list. > 2. It is not always possible, as client may be in a different network than > server nodes, so cluster nodes do not necessary know IPs of nodes, which > are valid for the client. > > Best Regards, > Igor > > > On Thu, Apr 25, 2019 at 7:25 PM Ken Cheng <kcheng....@gmail.com> wrote: > >> I am still on the design phrase of go thin client. once it's ready I will >> share the link. thanks. >> Thanks, >> Ken Cheng >> >> >> On Thu, Apr 25, 2019 at 10:02 PM Igor Sapego <isap...@apache.org> wrote: >> >>> Hello, >>> >>> Are you developing a Go thin client? Can you share a link? >>> >>> There is already one go client I'm aware of [1], is yours related >>> somehow? >>> >>> As for your question, thin client is given list of IPs and ports by a >>> user. During the start, >>> or in background thin client tries to establish connection to all of >>> them. Upon connection, >>> during handshake, it find outs node ID and associates it with given >>> IP:port pair. Thin client >>> should not try to establish connection with any address, which is not >>> given by a user. >>> >>> Does it helps? >>> >>> [1] - https://github.com/amsokol/ignite-go-client >>> >>> Best Regards, >>> Igor >>> >>> >>> On Thu, Apr 25, 2019 at 12:17 PM kcheng.mvp <kcheng....@gmail.com> >>> wrote: >>> >>>> Thank your information very much! >>>> >>>> >>>> >>>> -- >>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >>>> >>>
