Search:

Type: Posts; User: dalmy

Search: Search took 0.02 seconds.

  1. Replies
    5
    Views
    2,851

    First of all, we are not using web pages, but a...

    First of all, we are not using web pages, but a .Net thick client. First we establish the connection and then after we get the OK, we loop through and wait for each of the 55 subscriptions to return...
  2. Replies
    5
    Views
    2,851

    The latency is 500 ms each was for a RTT of 1000...

    The latency is 500 ms each was for a RTT of 1000 ms.

    The link is 256kbits per second.

    The data adapter(s) we are using are .Net data adapters created by us.

    For this test, the client is...
  3. Replies
    5
    Views
    2,851

    Problem with High Latency Links

    In my test environment I am running Lightstreamer on a server with a Packet Storm box between it and a client. The link is 256K and the latency is 1000 ms. It is taking a really long time to get...
  4. Thank you for your quick response. Do you plan...

    Thank you for your quick response.

    Do you plan on adding compression to the .Net client in the future?

    Thanks.
  5. Wanting to use response compression with a thick .Net client

    We are trying to reduce the bandwidth needed for the data coming from lighstreamer to our .Net application. We have turned on compression on the server side, but when looking at the request header...
  6. Replies
    1
    Views
    2,582

    Metadata Adapter Question

    I am trying to create a Metadata Adapter to do single sign-on authentication for our client application. I have modified the LiteralBasedProvider.cs class in the provided examples, but one thing I...
  7. Problems connection .Net Desktop Client to Server using HTTPS

    When trying to log on to Lightstreamer from my .Net desktop application using HTTPS I receive an error.

    "SSL read error: Inbound closed before receiving peer's close_notify: possible truncation...
Results 1 to 7 of 7
All times are GMT +1. The time now is 04:11 PM.