From sgcWebSockets 4.4.3, Amazon AWS IoT MQTT component supports custom authentication, so from this version all MQTT protocols are supported. MQTT over WebSocketsMQTT over TCPX.509 certificate authenticationSignature V4 authenticationCustom Authentication Protocols Supported The following table lists the protocols that the AWS IoT devi...
eSeGeCe
software
From sgcWebSockets 4.4.3, the Amazon AWS IoT client supports Signature V4 Authentication, this means that you don't need to use a certificate to authenticate against AWS MQTT Server. Signature V4 can be used for MQTT over WebSockets and port 443. Configuration First you must create a new user in your AWS console and assign privileges for IoT device...
From sgcWebSockets 4.4.3, Bittrex API component supports latest WebSocket API V3. Prior API, end of life is planned for 09/30/2020. The API still is based on SignalR but there are several changes, so all old methods have been removed and new methods and events have been added. Private Methods There are some new private methods like Subscription to ...
httpbin.org provides a useful server to test HTTP/2 protocol, there are several cases which can be used to test HTTP clients. You can find below a list of main tests provided: HTTP Methods: Testing different HTTP verbsAuth: Auth methodsStatus Codes: Generates responses with given status codeRequest inspection: Inspect the request dat...
In a previous post, I show a comparison between HTTP2 and HTTP1 performance using a single connection (see HTTP2 vs HTTP1 performance). In this post I will show a comparative between HTTP2 and HTTP1 introducing a latency and showing how latency can affect to HTTP protocol requests. When a client do a request, there is a latency, more or less depend...
RFC 7540 and RFC 7541 contains the full specification of HTTP/2 protocol and in the process of implementing a new HTTP/2 client for sgcWebSockets library, is important to use external tools to check if client component is working as expected. One of this online tools is hosted in: https://http2.golang.org/ This web offers some tests for HTTP/2 clie...
From sgcWebSockets 4.4.2 Telegram is supported for iOS64 devices, which means that you can build your own telegram client. TDLib takes care of all network implementation details, encryption and local data storage. TDLib supports all Telegram features. TDLib (Telegram Database Library) Advantages Cross-platform: can be used on Windows, Android,...
A customer ask if TMS Sparkle and sgcWebSockets can run together, and the answer is yes, there is no problem running sgcWebSockets and TMS Sparkle on the same server. Both can run using HTTP.SYS server, you can run a single HTTP.SYS server and configure endpoints to run with Sparkle and sgcWebSockets without problems. Basically you configure i...
From sgcWebSockets 4.2.2 Binance Futures API is fully supported. 1. Added support for live subscriptions in websocket api. 2. Added support for user stream websocket data. 3. Added support for Rest API: 3.1 Market Data Endpoints: exchange information, kline, tickers... 3.2 Account / Trades Endpoints: send orders, get account...
Changes included in sgcWebSockets 4.4.1 [+] : Improved Telegram API Component, added support for Android. [+] : New property "DatabaseDirectory" in Telegram Client. Allows to set the directory where is the TDLib database. [+] : Improved Telegram Demo to ask user for a password if telegram component requires it. [+] : Improved speed reading websocke...