this is thread meant to collect some ideas. When working on an app for Android using Zeos and the Webservice driver, I noticed that yes - the app works and it works fast enough but it isn't as nice as I would it like to be. So I started wondering what changes would be necessary to get Zeos to do its work of fetching data outside the main thread and send events when data is available. Something like this:
The idea is to keep the GUI responsive while Zeos is waiting for data or processing large datasets. Also this could allow other background threads to use the same database connection to get their work done. Currently this kind of processing is not easily possible because Zeos as a whole is not thread safe. Creating the necessary thread safety is not easy for users and I would like for Zeos to make that kind of data processing possible without requiring each user to implement its own scheme for doing this. What are your opinions? Is this something that we should consider doing?
If so how could that be done? My current idea would be to wrap up most of the DBC layer into the worker thread because otherwise we would have to make all drivers and their components thread safe? Maybe we need something like the pooled driver that works a s a proxy but only with focus on thread safety? Or would we need to implement a new set of components (connection, datasets and the like)? Opinions?
Best regards,
Jan