I have a simple activex server component that is called from a client component over DCOM. Both components are developed in Visual Basic 6.0.
The client component is called from an asp page.
First I compiled the client component with the threading model set to "apartment threaded". When I ran the code, the creation of the server component took about 10 seconds each time. I then tried a lot of changes to the DCOM/COM+ settings on both the client and the server. Nothing helped.
When I recompiled the client component with the threading model set to "single threaded" the 10 seconds delay disappeared. But I don't want to keep it "single threaded" because that won't scale well.
How can my threading model affect DCOM response times and what can I do to get good response times using "apartment threading"?
Thanks
/dcom90
The client component is called from an asp page.
First I compiled the client component with the threading model set to "apartment threaded". When I ran the code, the creation of the server component took about 10 seconds each time. I then tried a lot of changes to the DCOM/COM+ settings on both the client and the server. Nothing helped.
When I recompiled the client component with the threading model set to "single threaded" the 10 seconds delay disappeared. But I don't want to keep it "single threaded" because that won't scale well.
How can my threading model affect DCOM response times and what can I do to get good response times using "apartment threading"?
Thanks
/dcom90