ADO.NET 與 flash

下面是從 Data Access with ADO.NET 一書中摘錄出來的片段。

有趣的地方在於 DAO, DataSet, dataProvider 這些名詞對flasher來說有沒有覺得很熟悉？
其它相關的還有data binding等等。

一開始我覺得這是”誰抄誰”(比較偏向 .net 抄java, mm抄.net) 的問題，不過後來想想好的概念與技術本來就會被大家相中來實作，所以mm採取類似的手法(甚至名詞)也就不足為奇了，簡單整理一下整件事的發展歷程應該是

java -> .net -> mm。

可惜的是ADO.NET本身功能強大又完整，是真正的 Data Access Object，而actionscript只學到了部份片毛跟名詞，剩下一切要自已來。(嘆)

Three versions of Visual Basic were released before any database access capabilities were provided with the program. Data Access Objects (DAO) technology was added with the release of Visual Basic 3. DAO enabled programmers to access local databases in the Microsoft Jet Database Engine format, which were primarily ISAM (Indexed Sequential Access Method) files. With DAO you could also access databases on a server, but I always found performance between a client and a server to be poor because DAO was optimized for local access.

After DAO came Remote Data Objects (RDO) and then ActiveX Data Objects (ADO). These data access technologies were designed for the client/server paradigm. With the movement away from a client/server model to an n-tier, loosely coupled design, a new data access methodology is required.

ADO.NET components have been designed from the ground up for faster data access and data manipulation in an n-tier environment. Two central components of ADO.NET accomplish this: the in-memory DataSet object and the .NET data provider. The data provider is a set of components that include the Connection, Command, DataReader, and DataAdapter objects. I’ll go into more detail about the DataSet object and the data provider objects shortly. First let’s see how ADO and ADO.NET compare.