Results 1 to 4 of 4

Hybrid View

  1. #1
    Ok, thanks for the info.

    With your knowledge, how would you rate the server to client performance for HTTP-STREAMING vs. WS-STREAMING ?

    Can we expect to see a 30% decrease in e.g. number of messages put through the channel or overall latency of individual messages - or would you expect it to be the same? (without applying GZIP for HTTP streaming).

    We looked briefly at implementing our own LS WS .NET client, by sniffing the LS/WS protocol using the JavaScript client, but it does not look as simple as we initially thought.

  2. #2
    Administrator
    Join Date
    Feb 2012
    Location
    Milano
    Posts
    716
    Actually we expect, that for typical scenario where the comunication is mainly FROM server TO client, the WebSockets do not offer any better performance than HTTP Streaming (neither for throughput nor for latency). The real advantage of WebSockets arises for bi-directional communication, that is, when you send low latency updates FROM the client to the SERVER.

    Anyway, the JavaScript Client library and .NET client library use a communication protocol with Lightstreamer server slightly different. The JS library is based on a private protocol (not documented), while the .NET library is based on the Network protocol for Generic Client , but at the moment it is not ready for WebSockets.

 

 

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT +1. The time now is 05:02 AM.