• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            隨筆 - 42  文章 - 3  trackbacks - 0
            <2025年7月>
            293012345
            6789101112
            13141516171819
            20212223242526
            272829303112
            3456789

            常用鏈接

            留言簿(2)

            隨筆檔案

            文章檔案

            網(wǎng)頁(yè)收藏

            搜索

            •  

            最新評(píng)論

            閱讀排行榜

            評(píng)論排行榜

            Recently, I have read Inside COM, it is not my first time to read it. But still I got some useful information from it.

            First of all, rather than inheriting, Containment and Aggregation are the two methods COM used to achieve reusability.
            Aggregation is the specialized form of Containment, in which the programmer doesn’t have to implement code in the outer component to forward/delegate a call to the inner component and hence makes the life of a programmer easier. In Aggregation, the outer component hands over the control of the interface, which is being implemented by the inner component, to the client directly and the outer component gets out of the picture. In Aggregation, the interface to the inner component is exposed directly to the client, which is in contrast with the Containment. The outer IUnknown and the Inner IUnknown will be having the different implementation of the QueryInterface and hence it violates the basic QueryInterface rules. To forward/delegate calls to the outer IUnknown, the inner component needs the outer component’s IUnknown interface pointer. The outer component passes its IUnknown interface pointer at the time of creating the inner component. The outer component calls CoCreateInstance and passes its IUnknown pointer in the second argument of CoCreateInstance. If this parameter is non-NULL, then the component is being aggregated, otherwise the component is not aggregated.

            Secondly, The IDispatch interface was initially designed to support Automation. It provides a late-binding mechanism to access and retrieve information about an object's methods and properties.In addition to the methods inherited from IUnknown, server developers must implement the following methods within the class definition of each object that is exposed:
            • GetTypeInfoCount returns the number of type descriptions for the object. For objects that support IDispatch, the type information count is always one.
            • GetTypeInfo retrieves a description of the object's programmable interface.
            • GetIDsOfNames maps the name of a method or property to a DISPID, which is later used to invoke the method or property.
            • Invoke calls one of the object's methods, or gets or sets one of its properties.

            When the client need to call the method provide by the server, and the code is like this:

             

             1HRESULT hret=CoInitialize(NULL); assert(SUCCEEDED(hret));
             2    CComPtr<IDispatch> ptr;
             3
             4    ptr.CoCreateInstance(L"InternetExplorer.Application");
             5      if(ptr==0{ wprintf(L"Unable to create Application\n"); return 1; }
             6    
             7    wchar_t *array=L"GoHome";
             9    long id;
            10    hret=ptr->GetIDsOfNames(IID_NULL,&array,1,LOCALE_SYSTEM_DEFAULT,&id);
            11    assert(SUCCEEDED(hret));
            12    
            13    DISPPARAMS noparams;  memset(&noparams,0,sizeof(noparams));
            14    
            15    hret=ptr->Invoke(id,IID_NULL,LOCALE_SYSTEM_DEFAULT,DISPATCH_METHOD,&noparams,NULL,NULL,NULL);   
            18    CoUninitialize();    return 0;
            19

            Third, Connection Points, Com’s Observer Pattern
            -Based on Callbacks
            -COM-Object can have one or more event sources
            -Per event source may be one or more subscribed event sink
            -asynchronous communication between a server and its clients

            //Client
            class myEventSink : public EventSink
            {
             void handleEvent(int arg)
             { cout << “myEventHandler” << arg << endl; }
            };

            //Server
            [ object, uuid(…) }
            interface IEventSource : IUnknown
            {
             HRESULT Attach( [in] IEventSink* PEveSink);
            };

            Protocol
            IConnectionPointContainer::FindConnectionPoint
            IConnectionPoint::Advise       //passing sink interface pointer, receiving cookie
            IConnectionPoint::Unadvice    //terminates notification

             

            posted on 2012-03-04 22:08 鷹擊長(zhǎng)空 閱讀(1238) 評(píng)論(0)  編輯 收藏 引用

            只有注冊(cè)用戶登錄后才能發(fā)表評(píng)論。
            網(wǎng)站導(dǎo)航: 博客園   IT新聞   BlogJava   博問(wèn)   Chat2DB   管理


            国内精品久久久久| 久久久久久极精品久久久| 久久国产精品77777| avtt天堂网久久精品| 久久九九免费高清视频| 亚洲精品高清国产一线久久| 国产精品午夜久久| 国产精品亚洲综合久久| 成人精品一区二区久久| 精品久久久久久亚洲精品| 综合久久久久久中文字幕亚洲国产国产综合一区首 | 2020久久精品国产免费| 91精品国产高清久久久久久91| 久久婷婷五月综合成人D啪| 久久99精品久久久久久不卡 | 久久亚洲AV无码西西人体| 人妻少妇久久中文字幕一区二区 | 午夜精品久久久久久毛片| 日批日出水久久亚洲精品tv| 久久亚洲精品视频| 久久99国产精品久久| 久久午夜羞羞影院免费观看| 亚洲国产精品无码久久久蜜芽 | 久久婷婷久久一区二区三区| 久久久久免费看成人影片| 狠狠色婷婷久久综合频道日韩 | 日韩欧美亚洲国产精品字幕久久久| 91精品国产乱码久久久久久 | 欧美一区二区精品久久| 成人久久综合网| 国产一区二区三区久久| 97精品久久天干天天天按摩| 国产亚洲欧美精品久久久| 精品国际久久久久999波多野 | 国产美女亚洲精品久久久综合| 一日本道伊人久久综合影| 一本色综合久久| 亚洲国产精品无码久久久秋霞2 | 久久综合给合久久国产免费| 亚洲成色WWW久久网站| 91精品国产乱码久久久久久 |