MQTT Publish Message and Wait Response

From sgcWebSockets 4.4.4 the MQTT client has a new method called PublishAndWait. Till now, when a client publishes a message using QoS levels 1 or 2, the only way to know if the message was processed by server was using the asynchronous events OnMQTTAcknowledgment or OnMQTTPubComp, this means that client must implement his own wait method to check ...

Continue reading

Google Calendar Client API V3

From sgcWebSockets 4.4.4, Google Calendar API is supported, the Google Calendar API lets you integrate your app with Google Calendar, creating new ways for you to engage your users. The Calendar API lets you display, create and modify calendar events as well as work with many other calendar-related objects, such as calendars or access controls. Mai...

Continue reading

sgcWebSockets 4.4.3

These are the features included in sgcWebSockets 4.4.3 [+] : Initial support for HTTP/2 in TsgcWebSocketHTTPServer - New property HTTP2Options: allows to enable HTTP/2 protocol and configure initial settings. [+] : Improved Bittrex API component, now supports latest V3 API. - New Methods: Subscriptions to Balance, Orders, Candles, Trades... - New E...

Continue reading

DataSnap with WebSocket and HTTP/2

From sgcWebSockets 4.4.3, you can replace your DataSnap server application by our WebSockets server and take advantage of new features like: WebSocket ProtocolHTTP/2 ProtocolIOCP There are 3 different types of server that you can use as a replacement of TIdHTTPWebBrokerBridge default Indy server.  Server Main Features Description TsgcWSHTTPWeb...

Continue reading

HTTP/2 Server Test Performance

From sgcWebSockets 4.4.3, HTTP/2 is initially supported and new features will be added on next versions. In a prior entry blog we compared the performance between HTTP 1.1 and HTTP/2 protocols, to do this, I use sgcWebSockets HTTP/2 client which downloaded 100 images from imagekit.io servers.  HTTP/2 Client  sgcWebSockets HTTP/2 clie...

Continue reading

HTTP/2 Initial Server Support

From sgcWebSockets 4.4.3 HTTP/2 protocol is initially supported (it's still on beta) from TsgcWebSocketHTTPServer. Fast HTTP.SYS based server will receive support for HTTP/2 on next versions. By default, HTTP/2 support is disabled, so you must enable before testing. There is a new property, called HTTP2Options, just set HTTP2Options.Enabled = ...

Continue reading

AWS IoT MQTT Custom Authentication

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...

Continue reading

AWS IoT MQTT Signature V4

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...

Continue reading

Bittrex API V3 Support

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 ...

Continue reading

HTTP2 Tests from HTTPBIN.ORG

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...

Continue reading

HTTP2 Latency

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...

Continue reading

HTTP2 Client Tests

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...

Continue reading

HTTP2 vs HTTP1 Performance

sgcWebSockets supports a wide range of protocols, HTTP/2 is the protocol which is in development right now.  HTTP 1.1 has been the most used HTTP Protocol and wide implemented in server and clients during the last 15 years. But as internet grows, applications and webs growed and the amount of loaded data increased, the shor...

Continue reading

iOS Telegram Client

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,...

Continue reading

WebSockets TMS Sparkle

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...

Continue reading

Binance Futures API

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...

Continue reading

sgcWebSockets 4.4.1

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...

Continue reading

Android Telegram Client

From sgcWebSockets 4.4.1 Telegram is supported for Android 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, Androi...

Continue reading

sgcWebSockets 4.4.0

 Changes included in sgcWebSockets 4.4.0 [+] : Added support for Rad Studio 10.4 Sydney. [+] : Improved Telegram API Component, added support for OSX64. [+] : Improved Telegram API Component, added support for Linux64. [+] : Improved Telegram API Component, use SetTDJsonPath to set the path of tdjson library. [+] : New Telegram Demo built with...

Continue reading

Rad Studio 10.4

I am happy to announce the immediate availability of support for Rad Studio 10.4 on sgcWebSockets library. Registered users can download latest beta from private account. Next release will include support from Delphi 7 to Rad Studio 10.4 versions. https://www.embarcadero.com/products/rad-studio/whats-new-in-10-4-sydney