• <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
            <2010年3月>
            28123456
            78910111213
            14151617181920
            21222324252627
            28293031123
            45678910

            常用鏈接

            留言簿(2)

            隨筆檔案

            文章檔案

            網頁收藏

            搜索

            •  

            最新評論

            閱讀排行榜

            評論排行榜

            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 鷹擊長空 閱讀(1238) 評論(0)  編輯 收藏 引用
            94久久国产乱子伦精品免费| 99久久国产综合精品成人影院| 91久久精品国产成人久久| 亚洲精品乱码久久久久久蜜桃不卡 | 久久精品国产福利国产琪琪| 久久亚洲精品中文字幕| 人妻无码中文久久久久专区| 无码人妻久久一区二区三区免费| 伊人久久大香线蕉AV色婷婷色| 亚洲精品第一综合99久久| 亚洲欧洲精品成人久久奇米网| 欧美日韩中文字幕久久久不卡| 一本久久精品一区二区| 精品一二三区久久aaa片| 麻豆成人久久精品二区三区免费| 久久精品久久久久观看99水蜜桃| 久久婷婷五月综合色奶水99啪| 久久AV高清无码| 91精品国产91久久久久久| 色偷偷88欧美精品久久久| 久久香蕉综合色一综合色88| 久久99精品久久久久久野外| 久久婷婷是五月综合色狠狠| 中文字幕久久精品无码| 97久久精品午夜一区二区| 999久久久免费国产精品播放| 理论片午午伦夜理片久久| 狠狠色丁香久久婷婷综合| 久久91精品国产91久久麻豆| 久久亚洲天堂| 国产精品18久久久久久vr| 亚洲国产香蕉人人爽成AV片久久| 久久久噜噜噜久久中文福利| 久久九九久精品国产| 嫩草伊人久久精品少妇AV| 狠狠色综合网站久久久久久久| 久久精品国产久精国产一老狼| 色综合久久天天综合| 丁香色欲久久久久久综合网| 精品综合久久久久久88小说 | 国产亚洲综合久久系列|