RealThinClient SDK is a software component for building reliable and scalable cross-platform HTTP/HTTPS applications with Delphi. Built with RealThinClient SDK, an application server can handle thousands of active connections in an efficient multi-threaded manner. Since its first public release in 2005, it has been extensively stress-tested and used by more than 1000 developers worldwide.

Designed to help you build RELIABLE & SCALABLE Internet-Ready Applications
RealThinClient SDK is a flexible and modular framework for building reliable and scalable cross-platform Applications with Delphi, designed for the Web by utilizing HTTP/S with full IPv4 & IPv6 support and built-in multi-threading, extensively stress-tested to ensure the highest stability. By using non-blocking event-driven communication with built-in thread-pooling, Applications built with the RealThinClient SDK can handle thousands of active connections by using a limited number of threads in a real multi-threaded environment, on all supported platforms.

Multi-Deployment: target Windows, Mac OSX, iOS and Android from a single code-base
Write one Project in Delphi and compile it as (a) robust stand-alone Client and/or Server for Windows, Mac OSX, iOS or Android, or … as (b) ISAPI DLL extension for MS IIS or Apache, or … (c) integrate your Application into third-party Message-based Servers like the NexusDB Server.

RAD: Write events, not interfaces
Everything you do with RTC is component-based, while all the code you will ever need to write is defined as events, so you can design your server and client applications, without the need to use wizards or write interfaces.

Easy MultiThreading: turn on/off with a simple switch
A very sophisticated Threading mechanism is built into all RTC Connection components, which allows thousands of active connections to be running in separate threads, all at the same time. And the only thing you need to do is change a simple MultiThreaded property to True. Then, any newly received connection will be handled by a thread pooling mechanism which saves valuable System resources, while still enabling nearly unlimited number of simultaneous connections at the same time.

HTTP(S): No Firewall problems
RTC Clients will never have to be specially configured to get through corporate firewall’s and reach the internet. Simply by setting the UseProxy property to True, Data Client connection will use a connection provider which uses the same settings to read and send its data to the internet, as MS Internet Explorer does for browsing the Web. This means that Clients can work in any corporate LAN and have full access to the internet.

Non-Blocking
Other than most other internet components, RTC connection components are non-blocking and event-driven. This means that, even when not using a multithreaded mode, your users will not be blocked (“Application Not Responding”) during communication between your client and the server. For each state change in the connection, there is an event that will be triggered.

Remote Functions-reusable, easy to write, easy to call
Implementing and using remote functions is as easy as writing local functions. You just place a RtcFunction component on your Form or a Data Module, set function name and write your OnExecute event. OnExecute event receives the Connection object, Function Parameters and a Result object. You just have to use the parameters passed to the function to prepare the result. The rest is done “under the hood” by RealThinClient components.

Strong encryption & automatic compression
RTC components provide built-in and easy-to-use strong encryption as well as automatic data compression when working with Remote Functions. Enabling or disabling strong encryption and/or compression for remote functions is completely transparent. Simply set Encryption and/or Compression properties on RtcClientModule and RtcServerModule components and leave the rest to RTC. No other chnages in code required.

Plug-In Framework-write your own plug-ins or use 3rd-party plug-ins
All Client and Server code you write using RealThinClient SDK is ready to be used as building blocks or plug-ins in any application that uses RealThinClient SDK. For example, you can combine a Web Server, Messenger server, Application server, Database server and your own functions in one Data Server, even when those components weren’t specially designed to share the same Server space. Because of the easy-to-use plug-in framework on top of which all RTC Components are built, you can link unlimited number of functionality and data providing components like RtcDataProvider, RtcServerModule and/or RtcDataServerLink to one Data Server connection component, enhancing that server’s functionality with each new component. And by keeping code in separate units (Data Modules), you can even provide your own plug-ins (and sell those plug-ins) to anyone who uses the RealThinClient SDK.

Non-Blocking
Other than most other internet components, RTC connection components are non-blocking and event-driven. This means that, even when not using a multithreaded mode, your users will not be blocked (“Application Not Responding”) during communication between your client and the server. For each state change in the connection, there is an event that will be triggered.

Remote Functions-reusable, easy to write, easy to call
Implementing and using remote functions is as easy as writing local functions. You just place a RtcFunction component on your Form or a Data Module, set function name and write your OnExecute event. OnExecute event receives the Connection object, Function Parameters and a Result object. You just have to use the parameters passed to the function to prepare the result. The rest is done “under the hood” by RealThinClient components.

Strong encryption & automatic compression
RTC components provide built-in and easy-to-use strong encryption as well as automatic data compression when working with Remote Functions. Enabling or disabling strong encryption and/or compression for remote functions is completely transparent. Simply set Encryption and/or Compression properties on RtcClientModule and RtcServerModule components and leave the rest to RTC. No other chnages in code required.

Plug-In Framework-write your own plug-ins or use 3rd-party plug-ins
All Client and Server code you write using RealThinClient SDK is ready to be used as building blocks or plug-ins in any application that uses RealThinClient SDK. For example, you can combine a Web Server, Messenger server, Application server, Database server and your own functions in one Data Server, even when those components weren’t specially designed to share the same Server space. Because of the easy-to-use plug-in framework on top of which all RTC Components are built, you can link unlimited number of functionality and data providing components like RtcDataProvider, RtcServerModule and/or RtcDataServerLink to one Data Server connection component, enhancing that server’s functionality with each new component. And by keeping code in separate units (Data Modules), you can even provide your own plug-ins (and sell those plug-ins) to anyone who uses the RealThinClient SDK.

OR GET THIS FILE WITHOUT PLATINUM MEMBERSHIP - PRICE 80$ ONLY