Author:Akos Somorjai
Posted: Wed Jan 04, 2017 11:31 am (GMT+1)
Yes, because for example the main thread could be in the middle of a database transaction, where the internal state of the application is not consistent.
Also the API uses a few globals![Sad]()
We don't plan further development in this area at the moment, having two different solutions already (see my previous comment).
Best, Akos
Posted: Wed Jan 04, 2017 11:31 am (GMT+1)
| mar_kq wrote: |
| Thank you all for the replies, the Problem is for the Moment resolved. Do you consider this mechanism unadvisable even though the WPF Form will call exclusively read-only functions? Is there some kind of Roadmap for further developing concurrency? |
Yes, because for example the main thread could be in the middle of a database transaction, where the internal state of the application is not consistent.
Also the API uses a few globals
We don't plan further development in this area at the moment, having two different solutions already (see my previous comment).
Best, Akos