Search:

For a COMMAND mode item, the Server keeps the state of the table that results from the ADD, UPDATE and DELETE commands received.
In this way, a new client that subscribes to the item can receive the...

The Server log shows that the Server sends 5 update events, that are supposed to add 5 rows in your browser table.
If you can see 5 invocations to "onItemUpdate" on your NonVisualTable, then...

If I understand well

you run your page
the page loads and it is filled with pushed data
you come back after more than 3 minutes
the page is still full of pushed values
you hit the browser...

So, you have managed to get the desired behavior by resorting to a NonVisualTable, with client side filtering.
Ok. I hope that the data that gets filtered out is not too much, because this could...

Your Data Adapter currently supplies an item called "NewUser", i.e. the Subscribe method recognizes the "NewUser" name and supplies data accordingly. All other items needed, as "eventAdetails" and...

The whole discussion is becoming complex and I would like to avoid any misunderstanding.
Let me go back one step.

What you cannot do with a DynaMetapushTable or MultiDynaMetapushTable is to...

The solution on my previous post still applies.
It requires that your Data Adapter supplies an item for each event. The second page subscribes to exactly the required items. Each item supplies a...

I'm glad it works. If the data you see is what you expect, I won't investigate on the apparent inconsistencies in the Server log.

About the grouping feature, I suppose that the list shown in the...

With respect to the previous log, the "unfiltered" mode has caused the Server to send data to the client, as the "RELEASING DATA" lines show.
Did you see all those data in the direct loading case...

I expected to see more log, but the snippet clearly shows that a filtering operation was performed by the Server.
The two updates received in fast sequence, with an ADD and a DELETE for the...

We expect no difference between a Pushpage that is recalled directly in the browser and a Pushpage that is included as an iFrame.
Ensure that the url used to load the page is the same in both cases....