Search:

Amazing! 😄

Hi Tomas,
You are right. Lightstreamer uses log4back instead of log4j and is not vulnerable to Log4Shell exploit.
We will send you an email with more details in a while.

Hi all,

I'm very excited to let you know that we have released the beta version of the brand new Swift client library for Lightstreamer.

It's implemented natively in Swift and available as open...

Unfortunately, the Flutter/Dart client library has not been planned, yet.
An idea could be to try a tool like https://www.kotlinresources.com/library/jtransc/ to get a Dart lib from the Java lib.

Hi,

A flutter/dart client is in our roadmap, but not in the very short term.

Thanks

Can you please expand on your issue?

You might also want to check out this old post, which contains some code:
https://forums.lightstreamer.com/showthread.php?65-Using-selectors

Server version is reported in the header of the HTTP response, unless explicitly removed from the configuration of the server.
So, your client might do a simple HTTP request to the Lightstreamer...

I think there is a misunderstanding. TLCP-2.0.0.lightstreamer.com is the WebSocket subprotocol (for the sake of precision, it's called the Sec-WebSocket-Protocol), it's not the address to connect to.

You need to use the address of your Lightstreamer Server. If you don't own a Lightstreamer Server, I guess you wish to connect to a third-party installation. In such case, you should refer to their...

Great, thanks for the update!

That's great news, thanks!

@toolbox: Yes, we agree that it's good to keep this thread open, as this discussion is quite interesting to several Lightstreamer users.

Thanks,
Alessandro

5) To directly answer your question, there are no significant disadvantages to use the old protocol.

The documentation of the right version of the network protocol used by IG is linked on IG's site: https://labs.ig.com/lightstreamer-downloads

The link sends here.

Hi Jack,

The current version of Lightstreamer (6.0.x) supports two client protocols:

- Text Protocol: it works over HTTP; it's publicly documented; it is used inside most of the official...

We've discovered this project online:
https://rubygems.org/gems/lightstreamer

We haven't tested yet, but it looks like a promising start for a Lightstreamer Ruby Client. Well done!

We usually suggest to avoid putting a reverse proxy in front of a Lightstreamer Server, as it could negatively impact on performance. In particular, the reverse proxy might result as a bottleneck...

We are working on it. Will let you know soon.

Hi,

At present, only the JavaScript client libraries (for both web browsers and Node) use WebSockets, in addition to HTTP, while the other libraries use HTTP only. But support for WebSocket in the...

Streaming and polling can be combined with HTTP and WebSockets, so that all the combinations are possible and make sense. So:
1) Streaming over HTTP
2) Streaming over WebSocket
3) Polling over...

A JavaScript library is provided, which can run in any existing browser, including mobile, and in Node.js. The library exposes the full JMS API. Any HTML page can easily become a JMS client, able to...

You can add very fine-grained authentication and authorization to your Web JMS clients without dealing with legacy and proprietary JMS security mechanisms. The Lightstreamer JMS Extender offers a...

@jpsauvager, as mentioned in a previous post, you might want to check out the new version of the iOS API for Lightstreamer (the Unified Client API). It throws no such exceptions but rather delivers...

http://blog.lightstreamer.com/2015/12/introducing-lightstreamer-jms-extender.html