Download TMS XData v5.8 Full Source for Delphi XE2- Delphi 11 Alexandria

TMS XData v5.8 Full Source for Delphi XE2- Delphi 11 Alexandria

TMS XData v5.8 Full Source for Delphi XE2- Delphi 11 Alexandria
TMS XData v5.8 Full Source for Delphi XE2- Delphi 11 Alexandria


Delphi framework for multi-tier REST/JSON HTTP/HTTPS application server development and ORM remoting.

Feature overview
Server based on REST/JSON architecture style
Easily accessible from different client platforms like .NET, Java, jаvascript, since it's REST/JSON based
Uses standard POST, GET, PUT and DELETE HTTP methods for data request and data modification operations
Partial update of objects (PATCH)
Full-featured query mechanism
Multi-Model design makes it easy to create multiple servers with different mapping, types and service operations
Service Operations allow adding custom business logic to your server using interfaces and methods
Well-defined JSON representation of resources including entities, associations, streams and proxies
Support for streams (blobs)
Several databases supported in back end: SQL Server, MySQL, PostgreSQL, Oracle, Firebird, etc.. (through TMS Aurelius)
Design based on standard OData protocol
Based on TMS Sparkle HTTP/HTPS server architecture, which provides:
HTTP(s) server based on Windows http.sys stack
Support for HTTP Secure (HTTPS)
Kernel-mode caching and kernel-mode request queuing (less overhead in context switching)
Multiple applications/process can share (respond) the same port (at different addresses)
Secure Sockets Layer (SSL) support in kernel-mode
Feature details
TMS XData is a full-featured Delphi framework that allows you to create HTTP/HTTPS servers that exposes TMS Aurelius objects through REST/JSON.

v5.8
Improved : URL/Query parameter not flagged as required in Swagger UI, when such parameter comes from a DTO property (a DTO flagged with FromQuery attribute).
Improved : Design-time components were greyed out in component palette if current platform was different than Win32.
Fixed : TXDataClient not retrieving error message details in some situations (error 404 for services that didn't return objects)
Fixed : Swagger documentation for DTO members were not being displayed when if the members were declared in an ancestor class.
Fixed : Some wrong JSON request bodies were still causing status code in response to be 500 instead of 400.
Fixed : Some Access Violation error when lists were nil in DTOs.
Fixed : Service operations flagged as www-form-urlencoded were not decoding the plus sign (+) as spaces from request body.


  • 66