eSeGeCe Blog
Release notes, deep dives, and tutorials for sgcWebSockets, sgcHTML, sgcOpenAPI, sgcSign, sgcBiometrics, and sgcIndy.
Release notes, deep dives, and tutorials for sgcWebSockets, sgcHTML, sgcOpenAPI, sgcSign, sgcBiometrics, and sgcIndy.

Here is the comprehensive list of new features and bug fixes included in sgcWebSockets 4.4.6:[+] : New Event OnBeforeForwardHTTP on Server Components, allows to forward an HTTP request to another ser...

From sgcBiometrics 2.0, Facial Recognition is supported using a compatible Windows Hello camera, this allows to monitor if there is a human person in front of the camera (you can know if there is som...

Compiling sgcWebSockets in Rad Studio 10.4.1, some users reported problems compiling under OSX64, they get this error:Directory not found for option 'Lc:\Program Files (x86)\embarcadero\studio\21.0\r...

sgcWebSockets supports HTTP/2 protocol on Server and Client components, implementation is made in 100% pure Delphi code without using any external library. We have tested our HTTP/2 implementation us...

Here is the comprehensive list of new features and bug fixes included in sgcWebSockets 4.4.5:[+] : New Component TsgcHTTP_OAuth2_Server, server implementation of OAuth2 protocol, allows to Authorize...

When an OAuth2 client do a request to get a new Access Token, a Web-Page is shown in a web-browser to Allow this connection and login with an User and Password.The HTML page is included by default in...

By default, when OAuth2 is enabled on Server Side, all the HTTP Requests require Authentication using Bearer Tokens.If you want allow some URLs to be accessed without the need of use a Bearer Token,...

Before a new OAuth2 is requested by a client, the App must be registered in the server.Register a new App requires the following information: App Name: is the name of the Application. Example: MyApp...

By default, the OAuth2 Server uses the following Endpoints: Authorization: /sgc/oauth2/auth Token: /sgc/oauth2/tokenWhich means that if your server listens on IP 80.54.41.30 and port 8443, the full O...

From sgcWebSockets 4.4.5 OAuth2 protocol is supported on Server Components.OAuth2 allows third-party applications to receive a limited access to an HTTP service which is either on behalf of a resourc...

Worldpay offers direct integration using WebSockets + STOMP protocols. You can access to Worldpay API using sgcWebSockets library, just need a TsgcWebSocketClient and STOMP Protocol client in order t...

From sgcWebSockets 4.4.4 a new property Monitor has been added to WatchDog feature, WatchDog.Monitor allows to verify if new clients can connect to server, this is done by an internal client that tri...

These are the features included in sgcWebSockets 4.4.4[+] : New Component TsgcHTTPGoogleCloud_Calendar_Client, allows to use Google Calendar API V3: get Calendars, events, synchronize with your own c...

From sgcWebSockets 4.4.4, the Telegram Client supports Proxy connections. Telegram Client can be configured to make of use of a proxy. Currently, Telegram supports 3 types of proxies:1. HTTP2. MTProt...

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

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

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

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

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

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

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

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

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

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