TMS RemoteDB Set of Delphi components lets you make high-performance, cross-platform, scalable, 3-tier database software.
TMS RemoteDB permits you to create database programs that execute SQL operations on a remote HTTP server rather than a database server, utilizing a TDataset descendant. This makes it effortless to convert existing Delphi client-server software into 3-tier software with nominal source code changes.
TMS RemoteDB Amazing Characteristics:
Optimized memory utilization
Keeps present component behavior (such as TFieldDefs, by Way of Example )
Demands minimal code change in the customer application
The RemoteDB Server is a Delphi application/service that listens to HTTP requests. When customers work asks, the RemoteDB Server will forward the requests to the database being used, with the designated database-access component. The SQL is done, and the results are returned to the customer. You may select the elements that will conduct the SQL statements by a wide range of choices like FireDac, dbExpress, dbGo (ADO), amongst others, using part adapters. The SQL database could be any database supported by the elements used and have to be thread-safe (many are).
In the Delphi client program, you can utilize as many TXDataset elements as you want to execute the normal SQL operations. All TXDataset elements are connected to some TRemoteDBDatabase part using a Database property. The RemoteDBDatabase part is the one in charge of forwarding the SQL requests into the RemoteDB Server and regaining the values. All customer operations are transparent and like every TDataset use: you define the SQL statement, Open the dataset (or ExecSQL), specify the listing TField elements, Params, join TDatasource elements to it, etc...
Wide assortment of Database Component accessibility at Server-Side
When constructing the host, you may use a vast array of database-access elements to connect to a database. This has many benefits:
You can utilize your current know-how on a particular part set;
it is possible to fine-tune your server with particular options your parts provide for you;
Your customer application will act exactly like the part you are using on both sides. This gives you a much larger compatibility and effortless transition into TMS RemoteDB. If your current customer application utilizes FireDAC, as an instance, you may use it on the server-side, which makes your client-side TXDataset behaves almost exactly like a TFDQuery. It is the same for the rest of the components supported by TMS RemoteDB.
HTTP customer accessible Windows, macOS, iOS, and Android
Support for HTTP Secure (HTTPS)
Transparent handling of chunked and gzip-encoded answers
HTTP server based on HTTP.sys stack (Windows only - minimal Vista and Server 2008)
Support for HTTP Secure (HTTPS)
TGenericDatabase part for direct database host relations, in a Conventional client-server architecture
Kernel-mode caching and kernel-mode request queuing (less overhead in context switching)
Multiple applications/process can discuss (respond) exactly the Exact Same interface (at different addresses)
Secure Sockets Layer (SSL) support in kernel-mode
TMS Aurelius Integration
If your program is already utilizing our ORM frame, TMS Aurelius, for database access, then which makes it a 3-tier program with TMS RemoteDB will need merely a couple of lines of code. TMS Aurelius supplies a new adapter for RemoteDB. It is possible to use the link for a database (IDBConnection port ) similar to other alternatives, including FireDac and dbExpress. UniDac, etc... You do not have to change one line on your Aurelius program - change the link to use TMS RemoteDB also become 3-tier.
Supported Data-Access parts
Advantage Database server
Click on the below link to download TMS RemoteDB Full Source NOW!
Write your comment!
Access Permission Error
You do not have access to this product!
Dear User! To download this file(s) you need to purchase this product or subscribe to one of our VIP plans.