![]() Instead, we have to look at the DataSetProvider component-sending the data in response to requests for data. For this, we won't look at the ClientDataSets (requesting and receiving the data). To start to work on this problem, it's necessary to identify the amount of data that is actually sent over the wire. Many DataSnap Clients can be connected to a single DataSnap Server, all requesting data from the server, which is responsible for the data throughput bottleneck that can occur. The DataSetProviders export the data to the outside world, and the ClientDataSets receive the data (and send requests as well as updates back to the DataSetProvider). Instead of a ClientDataSet, you can employ XMLBroker components, which are specifically used in InternetExpress Web server applications. A DataSnap application consists of two tiers: the DataSnap Server, with a remote data module that has one or more DataSetProvider components on it, and a DataSnap Client, with an xxxConnection component and one or more ClientDataSets connected to the DataSetProviders.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |