Three layer and two layer are there are two advantages, one is to support many of the client, exceed certain limit two layers of the database connection, the server will be unable to stand; The second is the need of network security, the database server can row in the data area, the general client cannot direct database, which can connect the mid-tier server, will be divided into three layers of the presentation layer, logic layer and persistence layer I don't quite agree with, because the two layers have been able to solve the problem of logic encapsulation, if the middle layer encapsulation logic, will be very slow, and the three layer simplifies the system maintenance, I don't agree, because the two layers, three layers can do online upgrade, and three layers compared with B/S structure has the advantage that the client can do operation is flexible, the client hardware resources can be fully used, now I'm doing a set of three layer development VCL components, the goal is to do it like a two layer program development three layer application development, has now completed 70% of the construction, [email protected] QQ: 835730950

CodePudding user response:

We are all waiting to see the building work,,,,,,,,

CodePudding user response:

Three layer is just a beautiful legend

CodePudding user response:

Three layer is not a legend!
Ha ha!

CodePudding user response:

reference 1st floor response:

we are all waiting to see the building work,,,,,,,,

Also slowly moved a stool, etc

CodePudding user response:

Three layers, the second floor, on demand, can't say that good, demand is high, can only use three layers, such as customers, security, convenient maintenance, development and the development cycle, and so on, these factors determine, expect to make the three layers of the DEMO, ha ha,

CodePudding user response:

Looking forward to epic..

CodePudding user response:

See some netizens attention TCPDAC, a brief introduction, now can only capture several development testing interface,
The middle tier and database connection with UniDAC, middle layer and the client with Indy, have the following controls:
TCPDBServer: encapsulates UniConnection and Indy idTCPServer, support the database connection pool,
TCPDBClient: encapsulates the Indy idTCPClient, used for the transmission of SQL commands and results,
TCPQuery: database component, can Open the database table (Open), and executing SQL statements (ExecSQL), the design period can Open,
TCPDBClient want to support things, some things only do half,
Plan and TCPStoredProc TCPScript, TCPScript function with UniScript close,
Now does not support CacheUpdate, is expected to be UniDAC launch next version to support,
At present is to Oracle database development,
Screenshots link: http://download.csdn.net/detail/runsheng678/4508627

CodePudding user response:

The building work,,,,,,,,

Also moved a stool

CodePudding user response:

Indy, position high enough

CodePudding user response:

Three layer is divided into the presentation layer, logic layer and persistence layer?
That is another such as MVC layered

Delphi 3 layers, multi-level, many is a layered network architecture: add a middle layer between c and s (socket or web server/app)
Of Midas, ast and so on, is for the sake of Delphi as simple 3 development and 2 layers, but weak

I also do a set as a web app (isapi) as the framework of the middle layer, only development pattern is not visible when the design, but the runtime query request, rights deleted, just to avoid the direct database

CodePudding user response:

Upload a Demo:
http://download.csdn.net/detail/runsheng678/4674706

CodePudding user response:

Your this package is not conducive to object-oriented development, I suggest should give full consideration to use CLEINTDATASET this control,

CodePudding user response:

Because of a simple SQL statement processing for details of a field, such as various calculated fields and related fields, and so on,

CodePudding user response:

Without considering CLEINTDATASET, because my TCPQuery itself is designed for three-tier architecture, plan the next version support CacheUpdate TCPQuery support related fields and the main table,

CodePudding user response:

A beautiful legend

CodePudding user response:

Layer 2, or add a ws lu too...

CodePudding user response:

Ha ha,,,,,,,

CodePudding user response:

Recommended XE3 DateSnap, it can support multiple operating systems, and the server can respond to the TCP/IP, HTTP, client support desktop, WEB and kitchen table,,,,

CodePudding user response:

Support to discuss, later may also access to the database

CodePudding user response:

Collate a little busy recently, will TCPDAC for XE2 released, and with a demo,
http://download.csdn.net/detail/runsheng678/4812549

CodePudding user response:

Well, learn from the landlord

CodePudding user response:

In fact, I'm doing three layers

CodePudding user response:

To: lyhoo163
DataSnap is good, but to develop some trouble, as well as a database table controls, to decorate in the DataSnap several controls, and the program not only to move the client modification upgrades, synchronization and modified layer, two layer system upgrade to the old three-tier system is difficult, that is the reason why I why want to develop this set of controls,

CodePudding user response:

reference 24th floor runsheng678 response:

, lyhoo163
DataSnap is good, but to develop some trouble, as well as a database table controls, to decorate in the DataSnap several controls, and the program not only to move the client modification upgrades, synchronization and modified layer, two layer system upgrade to three layers of old system is very difficult, this is the reason why I why want to develop this set of controls,

I do as a web app (isapi) as the framework of the middle layer, can also make a general database gateway, the database structure changed, the middle layer without any modification
The client can also be done through ini configuration table structure of automatic adaptation, program do not need to modify