COM Design queries

[rbm1]

Hi All,

I'm a newbie to COM development, and I'm developing Com dlls for a project I'm currently working on.

I have a couple of questions relating to the implementation of com dll servers; specifically,

1. If I need to implement multiple unrelated objects/interfaces, should these be in separate dll's or is it okay for them to be part of the same COM object?

2. One of the interfaces my Com object exposes will need to also use Com in its implementation (ADO, which is what I'm hiding from the client). As the ADO com implementation of ADO lists 'Both' as the supported threading model, and I'm developing apartment threading objects, will this be okay? What I'm getting at is that I'll call CoinitializeEx(NULL, COINIT_APARTMENTTHREADED) (I know that CoInitialize(NULL) is equiv) from each thread that will use my Com object, which will then internally instanciate an ADO object. Will this work correctly?

TIA for advice/comments
Regards,
Richard

[shifrbv]

1. Single DLL can have up to 1024 interfaces...., each can have number of methods/properties

2. Basically "Both" means both: free to use with STA or MTA appartments

[rbm1]

Thanks for your reply,

But, I know that a dll can support multiple interfaces , I'm more interested in whether I should (from a good design point of view)..

Cheers
Richard