Using a polling refresh rate from a session custom property

If a gateway is using a session custom property of 600 in the polling by seconds, and multiple sessions are open, will they all be polling at the same time, or staggered by the amount that each opened initially?

I thought they would be staggered, but I am seeing an odd behavior where a lot of polling is happening at the same time.

I thought it would be better for me have polling set in the component.

What is best?

What kind of polling? now(...) or runScript(...) ? If those, they should be staggered, but fairly consistent.

In the binding, where it says polling fx seconds.

Though there are some in expressions using now( path *1000) to get to seconds.

Hmm. Not sure.

8.1.42 version

Hi so the lot of polling could he happening because it’s polling separately for every session.

Basically custom session properties will be individual polled for every session. Imagine you have a custom session parameter called “pollThis” and it’s polling per 5 seconds. and you have no session open so it won’t poll. Now let’s consider you have 1 session open with id seasion_001 it will have its own pollThis which will start polling every 5 seconds.
If you open another session with id session_002, it will again have its own pollThis (so basically 2 instances of pollThis) which will poll every 5 seconds. And this goes on for every session you open.

Ideally I would suggest you to always add polling part to the component so that it will only poll initially when that component is actually visible on the page.

1 Like

I meant that the session custom parameter is like 500 seconds.
Then that was fed into a query binding parameter in the view.

I think because each of the queries was referencing a session prop, that was causing the cache feature to not be used to not be used.

I think it is similar to what you described in nature, but the query was on the component using it I believe.

image
It had a variable in the polling area, I mean.