Igor, I just think that we're dealing with a trade off here, and that if we implement CQ for thin client, we will either end with a client that is not "thin" anymore, or semantics and guarantees of CQ would change so drastically that it would be a completely different feature. Either way, it's a big question weather there is a value in doing this.
I'm open to discussion though. If you have any particular suggestions, let's discuss them on dev list. -Val On Tue, Sep 11, 2018 at 5:26 AM Igor Sapego <[email protected]> wrote: > Guys, > > Personally, I do not see any problems, why we can not implement > Continuous Queries for thin clients. This will require a decent amount > of work, and will not give such strong guaranties as thick clients > give (for example, on server crash thin client will get an exception and > will need to re-register listener once again), but to me it seems totally > implementable. > > Val, > > Why do you think that such features are unlikely to appear in thin clients? > > Best Regards, > Igor > > > On Tue, Sep 11, 2018 at 3:07 PM Alexey Kuznetsov <[email protected]> > wrote: > >> >> Gordon, >> >> How about to start several client nodes "near" to cluster and use them as >> "proxies" for your desktop GUI apps? >> You may write some code that will push data from client node to you GUI >> app. >> This will require some coding of course. >> >> -- >> Alexey Kuznetsov >> >
