Search:

Hi jvanhensberg,

Please refer to the inline comments of <https_server> parameter in the "lightstreamer_conf.xml" configuration file in order to properly configure your Lightstreamer server.
You...

Hi chickendev,

So your problem is that you have changed the Data Adapter code, such that it no longer provides the snapshot, but then you also no longer receive the normal real-time updates?...

Hi chickendev,

Yes, if for a client session there are no real-time updates to send and after a configurable timeout no updates have been sent, then a small keep-alive message is sent.
The timeout...

Hi chickendev,

First of all let me clarify that isSnaphot is a flag, which is used to identify an event as a snapshot and differentiate it from all others which are considered real-time events....

Hi Nghiep,

About the ClassLoader, the isolation level of Adapter Sets can be configured in the adapters.xml file. Please refer to the classloader parameter of the provided template of adapters.xml...

Hi Nghiep,

Yes, I can confirm that multiple Adapter Sets can be plugged onto a single Lightstreamer Server.
So your plan of migration makes totally sense.

Regards,
Giuseppe

Hi chickendev,

What is available in the Metadata interface is the selector mechanism, which allows you to have, for a particular set of Items, a call to a Metadata method for each update received...

Hi rthompson,

Yes I can confirm that the feature has not been ported to c# remote library yet.
In this case you should consider the workaround suggested in this post:...

Hi rthompson,

Sorry, I missed to mention that in the specific case of terminating a subscription the callback to be invoked is in the TableInfo object paassed in the notifyNewTables.
In...

Hi rthompson,

Yes, please refer to this listener provided by the Lightstreamer server to receive requests about sessions and any asynchronous severe error notification: ...

At the moment we don't provide for the JMS Extender a ready made AMI as we do for the Lightstreamer server.
Anyway you can go through manual installation; once choosed your preferred operating...

Hi loksurya,

No configurations are needed, because notifySessionClose and unsubscribe should always be called.

Please consider that there should be no exceptions to this behavior; this is...

Hi Robert1,

The old web libraries used an undocumented private protocol specific to the javascript languages.
So it is not a good idea to try to reverse engineering that protocol in order to...

Hi baalbaki,

It seems that the two environments have different network infrastructures or anyway with substantially different behavior when shutting down a Lightstreamer server.

In the first...

Hi Megabyzus,

Thank you for the feedback about your integration process.

About your questions:

1. I can confirm that the combination of getSubscriptions and then getItems, as per your...

Hi Megabyzus,

The 'CONNECTED' prefix actually guarantees that a physical connection with the server has already been established.
Only in the 'CONNECTED: STREAM-SENSING' case, which should be a...

Hi Megabyzus,

As I said before it is not the expected behavior.
It is very strange that a subscribe call causes the failure of the connection attempt.

I think you need to investigate further...

Hi Megabyzus,

1. No, the subscribe requests should not interfere in any way with connection operations.
If a valid client session with the server is not established yet at the moment of the...

Hi Megabyzus,

1. I can confirm that generally it is a good practice to keep the LightstreamerClient object connected to the server and subscribe and unsubscribe dynamically accordingly with the...

Hi Megabyzus,

1.a There is no limit to the number of subscriptions a LightstreamerClient object can request.
Obviously considerations regarding the performance of the client application must...

Hi Chuck,

Yes, OnUpdate events are fired sequentially one after the other; this is why it is generally recommended that the processing associated should be fast and in cases where slow processing...

Hi baalbaki,

It is not very clear to me when you say "if in my client if onUnsubscrAll events are not called yet and I connect to another source":
did you mean that your client received the...

Hi baalbaki,

This is obviously not the expected behavior. Notifications of onUnsubscrAll events following a client session termination should all be simultaneous.
There is no configuration or...

Hi Matt,

I'm sorry that the instructions have been somewhat misleading for you.

In fact, in case of remote adapter deployment, in the folder there is only the configuration file with the...

Hi rvkvino,

Could you get more details on the reason for the refusal to open a new session for the client?
You could go through the server log, lightstreamer.log, looking for any refusal message,...