By default, the OAuth2 Server uses the following Endpoints: Authorization: /sgc/oauth2/auth Token: /sgc/oauth2/token Which means that if your server listens on IP 80.54.41.30 and port 8443, the full OAuth2 Endpoints will be: Authorization: https://80.54.41.30:8443/sgc/oauth2/auth Token: https://80.54.41.30:8443/sgc/oauth...
eSeGeCe
software
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 resource owner or by allowing a third-party application obtain access on its own behalf. Thanks to OAuth2, service providers and consumer applications can in...
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 to connect to this API Find below a sample code to connect to Worldpay using sgcWebSockets library Delphi Example // create websocket clientoClien...
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 calendar... [+] : New Demo GoogleCalendar which shows the main features of Google Calendar Client. [+] : New method "PublishAndWait" in MQTT Client, th...
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 tries to open a WebSocket connection to server, if fails, it restart the server. To monitor if clients can connect to server with a Time Out of 10 s...
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. HTTP 2. MTProto 3. Socks5 Add Proxy In order to configure a HTTP Proxy, first you must add the proxy to telegram configuration, to do this, just call Ad...
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 ...
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...
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...
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...