gt;> By executing these two test codes in the description, it is easy to
>> reproduce the problem.
>>
>>
>>
>> What should I do next? Continuously following this Jira?
>>
>>
>>
>>
>>
>> 发件人: Jeremy McMillan
>> 发送时间: 20
e two test codes in the description, it is easy to
> reproduce the problem.
>
>
>
> What should I do next? Continuously following this Jira?
>
>
>
>
>
> *发件人: *Jeremy McMillan
> *发送时间: *2023年5月24日 23:24
> *收件人: *user@ignite.apache.org
> *主题: *Re: Ignite thin
5月24日 23:24
收件人: user@ignite.apache.org
主题: Re: Ignite thin client continuous query listener cannot listen to all events
Thanks for bringing this up!
https://ignite.apache.org/docs/latest/key-value-api/continuous-queries#events-delivery-guarantees
This sounds like you may have found a bug, but
Thanks for bringing this up!
https://ignite.apache.org/docs/latest/key-value-api/continuous-queries#events-delivery-guarantees
This sounds like you may have found a bug, but the details you've provided
are not sufficient to help others recreate and observe it for themselves,
and this effort needs
Gordon,
Generally, having CQ on thin client would definitely be awesome. My only
point is that thin client has several technical limitations that would
introduce multiple "ifs" into the functionality. What exactly those ifs are,
and weather there is still value with all those ifs, is a big questio
-
From: vkulichenko
Sent: Tuesday, September 11, 2018 10:47 AM
To: user@ignite.apache.org
Subject: RE: Ignite Thin Client Continuous Query
Gordon,
Yes, generally we do recommend using thin client for such applications.
However, it doesn't mean that you can't us client node in case
are relaxed
for the user app. The key is to use the same (or useful subset of) the cache
interfaces.
From: Valentin Kulichenko
Sent: Wednesday, September 12, 2018 6:33 AM
To: user@ignite.apache.org
Cc: isap...@apache.org
Subject: Re: Ignite Thin Client Continuous Query
Igor,
I just think that
.
From: Alexey Kuznetsov
Sent: Tuesday, September 11, 2018 10:07 PM
To: user@ignite.apache.org
Subject: Re: Ignite Thin Client Continuous Query
Gordon,
How about to start several client nodes "near" to cluster and use them as
"proxies" for your desktop GUI apps?
You may write
Gaurav,
Web Console receives updates from web agent which periodically polls the
cluster.
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Guys,
Just wondering how does webconsole receievs updates from server
continuously?
Regards,
Gaurav
On 11-Sep-2018 10:31 PM, "Valentin Kulichenko" <
valentin.kuliche...@gmail.com> wrote:
> Igor,
>
> I just think that we're dealing with a trade off here, and that if we
> implement CQ for thin cl
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 b
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-
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
Gordon,
Yes, generally we do recommend using thin client for such applications.
However, it doesn't mean that you can't us client node in case it's really
needed, although it might require some additional tuning.
Would you mind telling if you have any other technology in mind? I highly
doubt that
To: user@ignite.apache.org
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
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
Hello,
This feature has not been planned yet as far as I know, I didn't manage to
find JIRA's for this, but I think discussion on this feature may be started
on dev list.
Regards
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
17 matches
Mail list logo
