Lightstreamer JS Client (6.1.3 / 7.x) - Deployment Config Matrix
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

View only
 
ABCDEFGHIJKLMNO
1
Client/Server host relationshipClient/Server protocol relationshipCookie requiredChrome / Firefox 8+ / Safari 6+ / IE 10+ / Edge / Opera 14+ / Android WebView / Samsung Internet IE 6 - 7 / Opera 12- / Opera Mini Firefox 3.6 - 7 IE 8 - 9 Safari 5 / Android Browser for Android 4.3- UC Browser for Android
2
---ConnectionServer-side requirementConnectionServer-side requirementConnectionServer-side requirementConnectionServer-side requirementConnectionServer-side requirementConnectionServer-side requirement
3
Common hostSame protocol(any)Streaming over WebSocketAn entry in the <cross_domain_policy> compatible with the server host is necessaryStreaming over HTTPnoneStreaming over HTTPnoneStreaming over HTTPnoneStreaming over HTTPnoneStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the server host is necessary
4
5
Insecure page to secure serverTRUEStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the server host is necessaryUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the server host is necessary
6
FALSEStreaming over HTTPnoneStreaming over HTTPnone
7
Secure page to insecure serverTRUENO connectionUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
8
FALSEStreaming over HTTPnoneStreaming over HTTPnone
9
10
Common subdomain with domain settingSame protocol(any)Streaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPA corresponding <allowed_domain> entry is necessary (or no entry at all). Moreover, if a cluster is in place and <control_link_address> is leveraged, and multihosting should be ensured, then <control_link_machine_name> has to be configured too. Streaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessary
11
12
Insecure page to secure serverTRUEStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessaryUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessary
13
FALSEStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
14
Secure page to insecure serverTRUENO connectionUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
15
FALSEStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
16
17
Different hosts / Common subdomain without domain settingSame protocolTRUEStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessaryUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessary
18
FALSEStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
19
Insecure page to secure serverTRUEStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessaryUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NStreaming over WebSocketAn entry in the <cross_domain_policy> compatible with the client host is necessary
20
FALSEStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
21
Secure page to insecure serverTRUENO connectionUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NUnoptimized Polling over HTTP<use_protected_js> set to NStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
22
FALSEStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessaryStreaming over HTTPAn entry in the <cross_domain_policy> compatible with the client host is necessary
Loading...