Greetings,
Would you have a design pattern for using SDAC with Omnithread with connection pooling?
I'm also having difficulty figuring out where to define the tmsconnection and coinitialize/counitialize within a service app. Since this is a service application, do I place the tmsconnection.create and coinitialize in the service start and the counitlialize in the service stop? Or do I place the tmsconnection instantiation, coinitialize and counitialize within the thread performing the SDAC insert?
Thanks,
Pat
SDAC Omnithread Design Pattern
Re: SDAC Omnithread Design Pattern
Thank you for your interest in our products. We don't have a demo showing how to use SDAC with OmniThreadLibrary.
You can call CoInitialize at application startup and CoUninitialize at application exit. To use connection pooling, you need to create a TUniConnection object per thread. See our documentation for more information about connection pooling:
https://www.devart.com/sdac/docs/work_pooling.htm
You can call CoInitialize at application startup and CoUninitialize at application exit. To use connection pooling, you need to create a TUniConnection object per thread. See our documentation for more information about connection pooling:
https://www.devart.com/sdac/docs/work_pooling.htm