• <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
            <2012年3月>
            26272829123
            45678910
            11121314151617
            18192021222324
            25262728293031
            1234567

            常用鏈接

            留言簿(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)  編輯 收藏 引用
            色综合久久久久无码专区| 久久精品视屏| 性做久久久久久久久老女人| 久久亚洲精品中文字幕三区| 国内高清久久久久久| 色狠狠久久综合网| 亚洲欧美一级久久精品| 精品久久久久久无码中文野结衣 | 国产成人久久AV免费| 久久亚洲私人国产精品| 久久久久久九九99精品| 久久精品国产清高在天天线| 午夜精品久久久久久久久| 久久国产免费观看精品3| 精品少妇人妻av无码久久| 久久精品国产亚洲77777| 91精品国产9l久久久久| 久久久中文字幕| 日本精品久久久中文字幕| 国产精品热久久无码av| 久久成人精品| 久久人人爽人人爽人人片av麻烦| 亚洲va国产va天堂va久久| 国产精品久久久久无码av| 久久精品视屏| 97久久国产综合精品女不卡| 色婷婷综合久久久中文字幕 | 2021久久精品国产99国产精品| 伊人久久大香线蕉精品| 久久婷婷人人澡人人| 色综合久久中文字幕无码| 97久久精品人人做人人爽| 亚洲欧美国产精品专区久久| 人妻无码久久一区二区三区免费| 久久精品一区二区国产| 精品国产日韩久久亚洲| 99久久综合狠狠综合久久止| 大香伊人久久精品一区二区| 国产精品欧美久久久天天影视| 亚洲精品视频久久久| 91精品国产综合久久四虎久久无码一级|