Hi, Could you please update on beow?
From: Naved Munde Sent: 15 December 2021 13:14 To: '[email protected]' <[email protected]> Subject: Re: Assigning specific name to thin client Hi, Can u elaborate the below mentioned points in more detail? 2, You can use ClientConfiguration.setUserAttributes to assign custom key/value pairs to a client instance. Those attributes are accessible on the server side. --> We want it to be accessible at any client either thin or thick client. How to achieve it? 3. For client-side only logic, there is no built-in way to assign a name to a client, but you can do that with a HashMap<IgniteClient, String> --> even if we assign HashMap<IgniteClient, String> to the thin client, then how do we access it from other thin/thick clients? ---------- Forwarded message --------- From: Pavel Tupitsyn <[email protected]<mailto:[email protected]>> Date: Fri, Nov 12, 2021 at 11:41 AM Subject: Re: Assigning specific name to thin client To: user <[email protected]<mailto:[email protected]>> Hi, If we are talking about Java thin client: 1. Automatic reconnect and retry is enabled out of the box. 2. You can use ClientConfiguration.setUserAttributes to assign custom key/value pairs to a client instance. Those attributes are accessible on the server side. 3. For client-side only logic, there is no built-in way to assign a name to a client, but you can do that with a HashMap<IgniteClient, String> On Thu, Nov 11, 2021 at 6:20 PM Ganguly Gundeboina <[email protected]<mailto:[email protected]>> wrote: Hi, Want to assign specific instance name to thin clients to monitor the clients. When thin client disconnected due to any reason, want to take manual action like starting the client. We are using 2.11, can we assign? Regards, Gangaiah "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment."
