Introduction

WebSockets represent a long-awaited evolution in client/server web technology. They allow a long-established single TCP socket connection to be established between the client and server, allowing bi-directional, full-duplex messages to be distributed instantly with little overhead, resulting in a very low latency connection.

 

Both the WebSocket API and the well as native WebSocket support in browsers such as Google Chrome, Firefox, Opera and a prototype Silverlight to JavaScript bridge implementation for Internet Explorer, there are now WebSocket library implementations in Objective-C, .NET, Ruby, Java, node.js, ActionScript and many other languages.

 

The Internet wasn't designed to be so dynamic. It was designed to be a collection of HyperText Markup Language (HTML) pages, linked together to form a conceptual web of information. Over time, static resources increased in number and richer elements such as images became part of the web fabric. Server technologies evolved to allow dynamic server pages - pages whose content is generated in response to a request.

 

Soon the need for more dynamic web pages led to the availability of Dynamic HyperText Markup Language (DHTML), all thanks to JavaScript (let's pretend VBScript never existed). In the years that followed, we saw cross-frame communication in an attempt to avoid page reloads, followed by in-frame HTTP polling. Things started to get interesting with the introduction of LiveConnect, then the forever frame technique, and finally, thanks to Microsoft, we ended up with the XMLHttpRequest object and thus Asynchronous JavaScript and XML (AJAX). AJAX in turn enabled XHR Long-Polling and XHR Streaming. But none of these provided a truly standardised, cross-browser solution for real-time, bi-directional communication between a server and a client.

 

Finally, WebSockets are a standard for bi-directional, real-time communication between servers and clients. Initially in web browsers, but ultimately between any server and any client. The standards-first approach means that we as developers can finally create functionality that works consistently across multiple platforms. Connection limitations are no longer an issue as WebSockets represent a single TCP socket connection. Cross-domain communication has been considered from day one and is handled within the connection handshake. This means that services like Pusher can easily use them to provide a massively scalable real-time platform that can be used by any website, web, desktop or mobile application.

 

WebSockets don't make AJAX obsolete, but they do replace Comet (HTTP Long-polling/HTTP Streaming) as the solution of choice for true real-time functionality. AJAX should still be used for short-lived web service calls, and when we eventually see a good uptake in CORS supporting web services, it will become even more useful. WebSockets should now be the standard for real-time functionality, as they provide low-latency, bi-directional communication over a single connection. Even if a web browser doesn't natively support the WebSocket object, there are polyfill fallback options that almost guarantee that any web browser can actually make a WebSocket connection.

 

 

sgcWebSockets is a complete package providing access to WebSockets protocol, allowing to create WebSockets Servers and Clients for .NET Applications.

 

• Fully functional multithreaded WebSocket server according to RFC 6455.
• Supports Windows 32 / Windows 64
• Supports MacOS 64.
• Supports Linux64.
• Assemblies for .NET FRAMEWORK (2.0+), .NET STANDARD (1.6+), .NET CORE (1.0+).
• Supports Chrome, Firefox, Safari, Opera and Internet Explorer (including iPhone, iPad and iPod)
• Multiple Threads Support. Indy Servers support IOCP or default Indy one thread perconnection model.
• Supports Message Compression using PerMessage_Deflate extension RFC 7692.
• Supports Text and Binary Messages.
• Supports Server and Client Authentication.
• Server component providing WebSocket and HTTP connections through the same port.
• FallBack support through Adobe Flash for old Web Browsers like Internet Explorer from 6+.
• Supports Server-Sent Events (Push Notifications) over HTTP Protocol.
• WatchDog and HeartBeat built-in support.
• Supports client Socket.IO connections.
• Supports Telegram Client.
• Binance Stock and Futures are supported (WebSocket, User Stream and REST APIs).
• STUN and TURN protocols are fully spported (client and Server components).
• Client WebSocket supports connections through HTTP Proxy Servers and SOCKS Proxy Servers.
• Events Available: OnConnect, OnDisconnect, OnMessage, OnError, OnHandshake
• Built-in Javascript libraries to support browser clients.
• Easy to setup
• Javascript Events for full control
• SSL/TLS Support for Server / Client Components (OpenSSL libraries required). OpenSSL 1.1.1 and 3.0.0 libraries are supported. Client supports SChannel for Windows.

 

 

 

Find below a list of the components included in sgcWebSockets Library.

 

1. sgcWebSockets
   • TsgcWebSocketClient: WebSocket Client based on Indy Library.
   • TsgcWebSocketServer: WebSocket Server based on Indy Library
   • TsgcWebSocketHTTPServer: WebSocket + HTTP Server based on Indy Library.
   • TsgcWebSocketServer_HTTPAPI: Fast Performance WebSocket + HTTP Server based on HTTP.SYS Microsoft HTTP API.
2. sgcWebSocket APIs
   • TsgcWSAPI_Binance: Binance Spot Client, supports WebSocket + REST APIs.
   • TsgcWSAPI_Binance_Futures: Binance Futures Client, supports WebSocket + REST APIs.
   • TsgcWSAPI_SocketIO: Socket.IO Client.
3. sgcWebSocket Libs
   • TsgcTDLib_Telegram: Telegram API Client.
4. sgcWebSocket Protocols
   • TsgcWSPClient_MQTT: MQTT (3.1.1 and 5.0) Client. Supports WebSocket and Plain TCP Connections.
   • TsgcWSPServer_AppRTC: WebRTC Server based on AppRTC Google Project.
   • TsgcWSPServer_WebRTC: WebRTC Server Protocol.
   • TsgcWSPClient_Files: WebSocket File Transfer Client Protocol.
   • TsgcWSPServer_Files: WebSocket File Transfer Server Protocol.
5. sgcWebSockets HTTP
   • TsgcHTTP_JWT_Client: JWT (JSON WEB TOKEN) Client.
   • TsgcHTTP_JWT_Server: JWT (JSON WEB TOKEN) Server.
   • TsgcHTTP_OAuth2_Client: OAuth 2.0 Client.
   • TsgcHTTP_OAuth2_Server: OAuth 2.0 Server.
6. sgcWebSockets P2P
   • TsgcSTUNClient: STUN Client.
   • TsgcSTUNServer: STUN Server.
   • TsgcTURNClient: STUN / TURN Client.
   • TsgcTURNServer: STUN / TURN Server.
7. sgcWebSockets AI