Search:

Hi James,

I can confirm that the Adapter Set is configured at the server-side and has to match with the one passed in the connection request of the client.
In your case you specify 'DEMO', that...

Hi James,

The 'CONNECTING' state of the client library is only temporary. In fact, within few seconds, you should find one of the three possible outcomes:

- connection successful,
-...

Hi Matthias,

Which version of the Python client lib are you using?
With latest version the instructions to activate the debug logging are these:...

The error message you're encountering, "Uncaught DOMException: The operation is insecure," is a security feature implemented by browsers. It usually occurs when you're trying to perform an operation...

It seems that in your client's environment, there is something interfering with the WebSocket upgrade requests.

Hi Ike,

This is strange, from the log you collected so far, it seems that the client send the we upgrade request bur receive a 404 error.
On the server side, it seems that the WebSocket upgrade...

Hi Ike,

In the log, there is no trace of the WebSocket protocol upgrade requests, neither successful nor any errors.
It's possible that there is an intermediary between your client and the server...

Hi Ike,

With the server log settings suggested in a previous post you should find these logs pertaining to a client session successfully bound to a websocket transport

26-Oct-23...

Hi Ike,

Unfortunately, switching to version 5.1.8 and enabling client-side DEBUG logging did not change the situation and did not help us understand the reason for the 404 error on the WS upgrade...

Hi ManKeer,

It is strange i have both replied to your emails. Anyway find below my first email:

Hi Mahmoud,

We have analyzed the various information you sent us, and what seems to emerge...

Hi ManKeer,

I have replied to your persoanal mail.

Regards,
Giuseppe

No, clients should not change anything when transitioning from in-process adapters to remote adapters, provided that the name of the adapter set and the data adapters remains unchanged.
However,...

I suppose that was the client buffer involved (few updates already received and not elaborated yet); or maybe is the snapshot of the new client session.
But please clarify if it is a browser...

By leveraging the notifyNewTables and notifyTablesClose methods of the Metadata you can maintain an updated map of users and their respective active subscriptions.
By adding the list of requested...

Hi ManKeer,

Thank you for the logs.
We have analyzed them and it appears evident that for the client experiencing delays, there are duplicate subscriptions.
In fact, the difference in the data...

Hi ManKeer,

Yes, server-side queuing occurs independently for each individual subscription of each user session. But as I mentioned, for MERGE-mode subscriptions, there is no server-side queuing...

Hi ManKeer,

Delays can have two different origins, either on the server-side or on the client-side.

If the origin is on the server-side, it would affect all clients indiscriminately first and...

Thanks for the feedback.

Regards,
Giuseppe

Hi,

Please could you share some more information about the problem you got with the Python client you have tested?
I.e. whether you are able to open a client session or not or only the data...

Hi Krishna Teja K,

I'm not sure if you've already come across this feature, but maybe it could be useful in your scenario:...

Hi Krishna Teja K,

Sorry but your scenario is not totally clear to me, but have you tried to use removeRow?

Regards,
Giuseppe

Hi Krishna Teja K,


You need to add 'click' in the fieldsList.

Regards,
Giuseppe

Hi Krishna Teja K,

Ok, so we need to understand why your client don't receive the "click" field as expected.
Please could you post here the code lines the client use to subscribe?
Are you able...

Hi Krishna Teja K,

The snippet of code you attached seems correct to me and the onclick should be actually updated.
Could you please try to trace if indeed your page receives the update with the...

Hi Krishna Teja K,

The snippet of code you attached seems correct to me and the onclick should be actually updated.
Could you please try to trace if indeed your page receives the update with the...