Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > C++ > in-process server considerations

Thread Tools

in-process server considerations

George2 George2 is offline
Senior Member
Join Date: Feb 2008
Posts: 108
Hello everyone,

Here is the comments from the book ATL Internals about in-process server considerations,

Any thread that calls CoGetClassObject or CoCreateInstance must already have joined an apartment, or the call will fail immediately. So, does that mean all objects exposed from in-process servers must be equally at home in single-threaded and multithreaded apartments so that random clients isn't cause harm? Fortunately, no.

Does it mean COM client (thread) and COM server no need to be the same type of thread model (e.g. STA, MTA, etc.)?

thanks in advance,
Reply With Quote

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Generating "most popular article" lists without crushing the server? ASP.NET caching considerations? ASP .Net 8 01-15-2007 12:25 AM
Any special considerations for making printable version of page? moondaddy ASP .Net 5 04-15-2004 09:22 PM
Confusing design considerations Will ASP .Net 4 01-26-2004 08:23 PM
Future Considerations Mr. Garrett Hord Microsoft Certification 1 01-09-2004 06:43 PM
Re: Performance considerations of compiling in debug mode, then NOT deploying the PDB file Steve C. Orr, MCSD ASP .Net 3 08-21-2003 01:29 PM