> If a async DB connection-component exists it would NOT be a > TDataSet descendent as everything around TDataSet expects call to be > synchronous. (Ex: If I call Open I expect the DataSet to be Open when > my call returns. If I call "Next" I expect to be on the next line OR I > expect the EOF to be turned True). The component not being an > TDataSet descendent would make it an highly specialized component > that's good for nothing but async DB stuff and can't be linked to data- > aware controls. Because of all those raisons I doubt such a component > exists! And if it does exist, I doubt it would provide the broad range of > interconnect compatibility you're requesting.
I don't agree with your opinion. I can work provided design is correctly done. It will work when you follow the "briefcase model". In this model, you decouple information move (download/upload) and information presentation. As an example, have a look at my MidWare component suite. In MidWare, you have asynchronous components to access an application server. Those component returns an in-memory specialised dataset (TMWBuffer). Another component (TMWTable if it matters) will simply present the TMWBuffer as a TDataSet suitable for DB-Aware controls. TMWTable gives access to the data contained in a TMWBuffer without actually moving the data. It's just a kind of presentation layer. btw: ADO component can do async operation. Never tryed becuase I do all my database stuff in the application server tier using MidWare as the asynchronous glue between the client and the appserver. -- [EMAIL PROTECTED] The author of the freeware multi-tier middleware MidWare The author of the freeware Internet Component Suite (ICS) http://www.overbyte.be __________________________________________________ Delphi-Talk mailing list -> [email protected] http://lists.elists.org/cgi-bin/mailman/listinfo/delphi-talk
