Jump to content

swingwin

Community Member
  • Posts

    31
  • Joined

  • Last visited

Posts posted by swingwin

  1. Hello,

    I've been using the PureDeal platform for several years. On this platform, it is possible to set alerts to receive an SMS when triggered.

    At the end of March, the PureDeal platform will be closed and I'll have to use the Web Platform (as personally announced by IG).
    But I haven't found where I can set the alerts to receive an SMS when triggered.
    I'm very annoyed because my trading uses SMS alerts.

    Where can I set up an SMS to be sent when an alert is triggered ?

    Sincerely

  2. Has anyone used this Lightstreamer Haxe library in .NET version?
    https://github.com/Lightstreamer/Lightstreamer-lib-client-haxe/tree/NET-v6.0.0-beta.2

    Does it solve the problem mentioned in this thread?

    The Haxe library is compatible with Lightstreamer Server since 7.3.2.
    But is it the case for the LightStreamer IG server because IG still hasn't given the version used on their servers?
    Sincerely

  3. I have completed the performance tests in periods of high volatility (US opening for example).
    The performances are excellent even if the solution found is a bit twisted.

    So I stay on this technical solution which works perfectly with Windows 7 and .NET.
    The solution is :
    API stream received by a compiled python application, which delivers the data on the workstation with a DDE server.
    Thus any application can connect to this DDE server and exploit the stream of the IG APIs (personal application with .NET, Excel, Matlab, etc...). No latency was observed.

  4. For now, I solved my problem so I can stay with windows 7 and keep my C# application intact.

    I developed a DDE server in Python interfacing with the IG APIs.
    I converted the Python application into an executable to improve performance.
    And I retrieve the DDE in C# (or Excel) with the NDde.dll assembly.

    I'll leave it at that for now and wait to test fast feeds in times of high volatility
    But if the performance is not there I'm considering doing the same thing with an RTD server and/or with Java.

  5. For .NET applications the problem is clearly located in the .NET Framework and the way the TLS1.2 protocol is set up in it
    So it is certainly not a problem linked to the "DotNetClient_N2.dll" library
    Indeed :
    - I made a test with the java application using the java library "sdk.client.java.se-5.1.1.1623.2.jar" ==> no connection problem and the data arrive correctly with the stream
    - I converted this java library to .NET assembly using IKVMC
    - my C#.NET application now uses the "sdk.client.java.se-5.1.1.1623.2.dll" library for lightstreamer connections, instead of the "DotNetClient_N2.dll" library
    and then the lightstream connection fails with the following error message

    "com.lightstreamer.ls_client.PushConnException: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake"

  6. @charlie303

    Another test that is increasingly pointing to problems with the lightstreamer .NET library.

    I just tested an old Python application, which I had archived in a corner.
    Well, the Python lightstreamer works fine in both demo and live version.

    For excel, I just checked and the excel solution provided by IG in the past is built on the "DotNetClient_N2.dll" library, and I do have the problem with Excel as the person who reported it a few days ago

  7. This evening I checked that the example and the java library were still working correctly.
    With the java app everything is operational with the DEMO server. The Lightstreamer connection is OK and the streams are returning data.

    And for this JAVA solution, the API session is created in version V2 (and not in version V3)

    In my opinion this confirms more and more that our problems with .NET are in the .NET lightstreamer DLL library.

  8. charlie303 wrote : "Is @swingwin still having issues?"
    Yes I have exactly the same problems as you, since also in my case I develop a C# windows forms application.
    The only difference with you is that I am using Visual Studio 2019 IDE and windows x64 configuration

    Everything was OK until December 2021, when the DEMO lightstreamer stopped working.
    And now since Sunday 15 May 2022, the lightstreamer LIVE does not work anymore.

    @teebeast: I tested your update this afternoon, but still no data is coming in through the DEMO and LIVE lghtstreamer

     

  9. Thanks Charlie for the detailed explanation.
    It's exactly the same problems on my side
    I also tried to create a new API DEMO key in the past, and had the same failure to create it.
    Maybe by doing a deactivation/activation of the existing API key the problem will disappear, but I don't dare to do the manipulation because I'm afraid of a definitive deactivation of this key.

    I am very interested in the feedback you will get from IG.

×
×
  • Create New...
us