04-16-2023, 11:01 PM
(This post was last modified: 04-16-2023, 11:04 PM by Alexandre Machado.)
In the next update (15.3.2) we are also including new and refactored Http client classes that are being used for all client communication from IW core classes:
- IWTelegram
- IWIPGeolocationClient
- IWOAuth
- IWReCaptcha
all these controls/classes need to establish communication with the API server via HTTP (mostly REST calls) in order to work properly.
We currently have a TIWHttpClient which is based on Indy. Indy is a solid framework for HTTP communication and works everywhere and we will continue to use it. This class has been renamed to TIWIndyHttpClient in new IW 15.3.2 (not yet released). A new class has been introduced, the TIWWinHttpClient, which is based on Windows WinHttp API. WinHttp is not available in older versions of Windows, but it can be used in all newer versions. WinHttp relies on Windows services itself to provide secure HTTPS. On the other hand, Indy relies on OpenSSL, so OpenSSL DLLs will likely need to to be deployed with your application, if using any of those controls/classes listed above with Indy-based client. This is not always desirable, that's why we are creating this new option. The new TIWWinHttpClient class will be available in all IW supported platforms, including Delphi 2009/2010/XE (they don't have the WinApi.WinHttp.pas which was released only in XE2).
ServerController will have 1 new property named HttpClientClass which can be set to WinHttpClient (default) and IndyHttpClient. Setting this property will control how IntraWeb core will handle the HTTP client communication for all those controls.
You can also use the same client classes to handle your own needs regarding Http client communication, instead of relying on 3rd party code, which simplifies the application code and maintenance.
Stay tuned!
- IWTelegram
- IWIPGeolocationClient
- IWOAuth
- IWReCaptcha
all these controls/classes need to establish communication with the API server via HTTP (mostly REST calls) in order to work properly.
We currently have a TIWHttpClient which is based on Indy. Indy is a solid framework for HTTP communication and works everywhere and we will continue to use it. This class has been renamed to TIWIndyHttpClient in new IW 15.3.2 (not yet released). A new class has been introduced, the TIWWinHttpClient, which is based on Windows WinHttp API. WinHttp is not available in older versions of Windows, but it can be used in all newer versions. WinHttp relies on Windows services itself to provide secure HTTPS. On the other hand, Indy relies on OpenSSL, so OpenSSL DLLs will likely need to to be deployed with your application, if using any of those controls/classes listed above with Indy-based client. This is not always desirable, that's why we are creating this new option. The new TIWWinHttpClient class will be available in all IW supported platforms, including Delphi 2009/2010/XE (they don't have the WinApi.WinHttp.pas which was released only in XE2).
ServerController will have 1 new property named HttpClientClass which can be set to WinHttpClient (default) and IndyHttpClient. Setting this property will control how IntraWeb core will handle the HTTP client communication for all those controls.
You can also use the same client classes to handle your own needs regarding Http client communication, instead of relying on 3rd party code, which simplifies the application code and maintenance.
Stay tuned!