Make your own free website on Tripod.com

DCOM

                    COM SERVICE ORGANIZATION

SY00932_.wmf (2596 bytes)

   

COM LIBRARY SERVICES TO WET YOUR API ! HUNGRY FOR COMS?

    COM Application Programming Interfaces: those hunger satisfying APIs!

        COM API requires both meat and vegetables with your meal: Co or the

            cook CoCreateInstance meals!

The cook always requests your response!             HRESULT of the taste of your meal.

SORRY FOR THE DESERT!yr2001.gif (9379 bytes)

You may Register your approval or compliant with the cook with the SYSTEM REGISTRY!

        COM meal IMPLEMENTATION LOCATES the Cook to inform him of his SERVICE!

                    Given you are COM food critic you register your response in a lookup table.

                            This table maps your tip identified by CLSIDs to the COM SERVER                                     

                                    FILENAME corresponding to your waittress!

This tip is Implemented by  CoCreateInstance to instantiate your tip COM Object!

Hit Counter

Here waitress considering your difficult work:

        hr = CoCreateInstance(CLSID_TipObject, NULL,

                CLSCTX_INPROC_SERVER | CLSCTX_LOCAL_SERVER,

                IID_ITipInterface, &pTipInterface);

SO00336_.wmf (66876 bytes)   If your waitress is happy with your tip, or she is not, she is not able to directly tell the cook.  Rather she informs the Manager of the restaurant who points to the cook.  The Manager is the Proxy for you the Client who Marshals your request by a STUB! In Process the STUB invokes an Interface with the cook and establishes communication.  The manager communicates with the cook and other employees with Local Procedure Calls (LPCs).

            If the cook is still at work the communication is LPC, however if the cook left in a hurry the manager must call up the cook with a Remote Procedure Call (RPC).  This RPC invokes DCOM!!!!!!!

DCOM FACTORY