ATL COM Client ?***(Urgent)

Dear codegurus,<BR>
What is the exact meaning of an "ATL COM Client"? One of the MS objectives for the VC++ Distributed Applications (70-016/70-015) explicitly mentions the following:
· Create an ATL COM in-process COM component and an ATL COM client to access it.
· Create an ATL COM out-of-process COM component and an ATL COM client to access it.

As per my understanding, the ATL COM client is like any other client application (.exe or .dll) ,that makes use of an ATL COM component . I normally create an AppWizard .exe as a client.
Or, is there a separate method of creating an ATL COM client?I am very confused with the terminologies.
Further, I would also like to know what would be the difference in a client that makes use of an in-process ATL COM component from the one that makes use of an out-of-process ATL COM component in VC++. I have found that in both of them we have to import the .tlb and use smart pointers to use the interfaces.

Please clarify my doubts. Its urgent !!

Hi,

As far as I know, there isn't a 'special' client for a COM server (even developed with ATL). The differences between clients using in-proc/out-of-proc COM servers are about what that client can DO with the servers.

Cosmin

An in-process component is one that shares the memory space of the client that is using it, typically a dll. In contrast an out-of-process component is one that runs in it's own memory space, such as an exe.

As for the clients, I can only guess that they want you to create a client capable of using the component. Your client can be written in any language that supports COM such as VC, VB or Java. To make life easy, VB is great for writing quick test apps.

HI,
As far as my knowledge goes, any application makes use of the readymade COM component can be a client.

If its a in process component its typically a DLL which sits in the same memory space as the client. Hence I guess in case of a in process dll the component has to be on the same machine as the client. An out of proc on the other hand is typically an exe and preferred in case of DCOM applications.