Ado. Net Data Access Mode

Microsoft has developed a new term, connection mode and disconnection mode. The dataset mode in the memory seems to have been available for a long time, and the clientdataset of Delphi seems to be in this structure. I still haven't seen any innovations in. net. In addition, ADO itself has such a client-disconnected DataSet object recordset. "dataset can manage multiple datasets and Their Relationships." This function also seems to have A recordset. However, I am not very familiar with the old version of recordset, because I used the ADO control of Delphi and did not use this function, so it is not convenient to comment casually. In fact, my concerns are: developing web with ASP. NET ProgramWhether the connection still needs to create a shared connection in the single-piece mode in the traditional C/S structure, or create your own connection on every page. in the C/S structure, the connection mode is still a good mode. in the B/S structure or distributed environment, the disconnection mode is better. On the one hand, the scalability is better, and on the other hand, the efficiency is relatively high, compared with the connection mode. The ADO. NET Framework also provides support for connection pools. I want to find out what kind of underlying support is for the connection pool. It seems that it is not using MTS, but a set of other things. The following is how to use connection transactions: Ado. Net also provides support for distributed transactions. A distributed transaction involves multiple database instances or databases in a transaction. COM + 1.0 (similar to the original MTS) to support this function. The interface is declared in system. javasiseservices. Another method is to declare the client as a subclass of the servicedcomponent class. To be included in the management scope of COM +. This class can be used only after registration.