Clarification of layer-3 databases and application servers

Welcome to the CC ++ programming community forum, and interact with 2 million technical staff to enter the application server to solve two problems. In the client server mode, the database server is responsible for connection issues (Xiang Yu encountered) 2. If the website wants to dynamically update data and the database needs to be connected to the Internet, there are other applications. Application in Model 1

Welcome to the C/C ++ programming community forum, and interact with 2 million technical staff> go to the application server to solve two problems: Client/Server mode: the database server is responsible for the connection problem (Xiang Yu brother encountered) 2. The website should dynamically update data and the database should be connected to the Internet. Other applications should not be mentioned. Application in Model 1

Welcome to the C/C ++ programming Community Forum and interact with 2 million technical staff> enter

The Application Server mainly solves two problems.
In a Client/Server mode: the database server is responsible for connection issues (Xiang Yu encountered)
2. The website needs to dynamically update data and the database needs to be connected to the Internet.
There are other applications.
In the first mode, the application environment is mainly in the LAN: Customer program + Application Server + database
The second mode is applied to the Internet: browser + WEB Server + Application Server + database
You can use browsers or client programs on the Internet.
It can be imagined that a large amount of data can flow in the LAN, and a small amount of data must flow in the Internet.

Where is the rule applied?
After using the application server, everyone agreed to accept the rules on the client.
Some people put the rules in the application server, which can reduce the workload of the database.
I think the rules still allow the database to be managed, and the database capability is better than ours.
Only a few very old databases have low management rules, maybe not relational databases.
The application server must process the rules.
The application server is best responsible for connection, data traffic monitoring, and providing quality services to clients,
Better compatibility with different types of old-fashioned databases.

There are currently three types of application servers
Microsoft's dispersibility: distributed to different technologies.
Database vendors: they sell application servers (dedicated type) together when selling databases ).
Independent Software Vendors: Independent Application Servers developed.
Suitable for different situations.
However, we want to develop independent application servers to provide better flexibility and compatibility.
Pay attention to the future during development.

C ++ Builder5 provides various parts for us to develop clients and application servers.
Application Server part: TDataSetProvider + BDE (Table, Query...) + ADO (ADOTable ....). Odbc still uses BDE parts; I have never seen it in SQL link.
ADO parts are not rich, without BDE sessions, batch movement, cache update, nested tables; no InterBase transactions, database information, monitoring, and events.
BDE is very complicated and disobedient when it is released, and even if there is an installer, it is not self-satisfied. I hope C ++ Builder6 can enhance the ADO function. Can I leave Deiphl6 blank?

Client
TDataSource + TClientDataSet + {TDCOMConnection; TSocketConnection; TWebConnection; TCorbaConnction; TSimpleObjectBroker}
There are five different ways to connect to the application server.
When TDCOMConnection is released using DCOM technology, you must pay attention to the NT Server Name and domain name settings, and the application server must also register DCOM on the client.

TSocketConnection: you do not need an NT domain name server in the TCP/IP mode. to connect to an application server with security issues, you must start ScktSrver. EXE to listen.

TWebConnection: HTTP is used, but it connects to the WEB server and transmits data to the application server. When the client is released, Wininet. dll only needs to be installed with IE3 and later systems;

[1] [2]