Thanks Val. We are currently using a client node in our desktop gui, but it performs very poorly when the latency to our server nodes is high. We also have other problems, such as when new client nodes join, the whole cluster will pause, which is unacceptable for an end user application. I raised a question about this a few weeks ago, and we were advised that client node is not intended for use in end user applications. Any sort of financial desktop application needs streaming data and event based updates. So it seems like ignite is of no use for this type of application. And now I wonder if there is much value for us to keep using ignite on the server side of our application, since we need totally different technology to enable streaming data and event based notifications on our client.
-----Original Message----- From: vkulichenko <[email protected]> Sent: Tuesday, September 11, 2018 7:43 AM To: [email protected] Subject: Re: Ignite Thin Client Continuous Query Gordon, Ignite thin client uses request-response model, which is not really suitable for functionality like this. I would never say never, but I think it's very unlikely that thin client would get any feature that imply pushing updates from server to client (this includes near caches, any type of listeners including continuous queries, etc.). If you have such a requirement, you should use client node instead. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/ This email and any attachments are proprietary & confidential and are intended solely for the use of the individuals to whom it is addressed. Any views or opinions expressed are solely for those of the author and do not necessarily reflect those of Nine Mile Financial Pty. Limited. If you have received this email in error, please let us know immediately by reply email and delete from your system. Nine Mile Financial Pty. Limited. ABN: 346 1349 0252
