Using the Persistence Provider with the Remoting Provider
The Persistence Provider can be used with a remote connection in conjunction with the Remoting Provider and your provider to load rowset data. This allows you to access data on any number of remote machines. The Remoting Provider is another OLE DB service component that interacts with your provider and your application. A copy of the Remoting Provider, your data provider, and the Microsoft Cursor Service for OLE DB must exist on each remote computer, and a copy of the Cursor Service, the Persistence Provider, and the Remoting Provider must exist locally.
The request (for refreshing or submitting changes) first goes through the local Remoting Provider. This provider then streams the data over a DCOM or HTTP protocol to the server's Remoting Provider, also called the DataFactory. The local Remoting Provider then waits for a response from the server.
The DataFactory, in essence, manages the rowset on the remote machine: It calls your provider with the request, loads the rowset into the server copy of the Cursor Service (caching the rowset data), and calls the server's image of the Persistence Provider. Depending on the action taken, the Persistence Provider streams the data or resulting message back over the network to the waiting Remoting Provider. This happens for each remote connection until the local copy of the Remoting Provider receives the response (message or rowset data) from the server or servers. Then the rowset can be loaded into the client cursor engine and made available to the application.
For more information, see the OLE DB Remoting Provider documentation.
.gif "using the OLE DB Persistence Provider remotely")
This topic is a part of: