This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
websockets [2015/01/04 19:12] mganzeboom created |
websockets [2021/05/07 11:51] (current) ctejedor |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| There are also libraries for various programming languages: | There are also libraries for various programming languages: | ||
| + | JavaScript: http:// | ||
| Python: http:// | Python: http:// | ||
| Java: http:// | Java: http:// | ||
| Line 22: | Line 23: | ||
| ===== Problems with WebSockets ===== | ===== Problems with WebSockets ===== | ||
| + | |||
| One of the things noticed in the DigLin and GOBL projects is that WebSocket communication is sometimes blocked by firewall / security software used in large institutions / corporations. Communication was altered to go through port 80 (HTTP), but still, at some companies WebSocket communication was blocked because of the sending of binary (audio) data. Firewalls cannot effectively scan binary data, so if set strict or not prepended by proper HTTP headers, the data packets are rejected. | One of the things noticed in the DigLin and GOBL projects is that WebSocket communication is sometimes blocked by firewall / security software used in large institutions / corporations. Communication was altered to go through port 80 (HTTP), but still, at some companies WebSocket communication was blocked because of the sending of binary (audio) data. Firewalls cannot effectively scan binary data, so if set strict or not prepended by proper HTTP headers, the data packets are rejected. | ||
| + | Also, a permanent connection to the server is established (more server-CPU load). | ||
| + | |||
| + | Low security. | ||
| + | |||
| + | Not all client-apps can use websockets. | ||