| http://dbpedia.org/ontology/abstract
|
IDispatch介面是组件对象模型（COM）中的标准介面，也称自动化（Automa … IDispatch介面是组件对象模型（COM）中的标准介面，也称自动化（Automation）接口，继承自IUnknown，用于讓其他函式使用协议。COM規格書規定COM物件应该是三种接口类型中的至少一种：
* 基于虚表（vtable）的IUnknown的定制接口；
* 分派（dispatch）的IDispatch接口以支持內觀資訊（introspection）。允许客户应用程序在运行时查出COM组件支持哪些属性与方法，即实现了运行期类型信息（RTTI）。客户应用程序编译时不需要知道COM的对象成员。脚本语言如VBS不能使用指针乃至函数指针，只能通过IDispatch接口访问COM组件。这是通过执行IDispatch接口中的Invoke方法。这是一种。与第一种定制接口相比，增加了內觀資訊与invoke的开销。
* dual接口，同时支持上述两种类型的接口增加了內觀資訊与invoke的开销。
* dual接口，同时支持上述两种类型的接口
, IDispatch is the interface that exposes th … IDispatch is the interface that exposes the OLE Automation protocol. Extending IUnknown, it is one of the standard interfaces that can be exposed by COM objects. COM distinguishes between three interface types: custom that are VTABLE-based IUnknown interfaces, dispatch that are IDispatch interfaces supporting introspection, and dual interfaces supporting both types. The Automation (IDispatch) interface allows a client application to find out what properties and methods are supported by an object at run-time, i.e. implements the concept of RTTI. It also provides the information necessary to invoke these properties and methods. Client applications do not need to be aware of the object members when they are compiled. This allows COM and ActiveX objects to be called by scripting programs platforms such as the ASP server and JavaScript on Internet Explorer, where calling conventions were not known at the time IIS or IE were built. By contrast, a simple object library is compiled and linked into a program, e.g. a DLL call needs to know a function name and parameters at compile time. A script writer can ask the COM object for a method or property it already knows about from documentation. Then, the client can execute the function with Invoke provided by the IDispatch interface, a form of late-binding. This sort of capability was also supported by Dynamic Data Exchange (DDE), which never became popular due to being too low-level. Dispatch interfaces are flexible, but suffer from additional introspection and invocation overhead compared to custom interfaces. It is therefore often a good idea to support both interface types with dual interfaces. That way, clients supporting VTABLE-based invocation can use the custom interface instead of the dispatch counterpart.rface instead of the dispatch counterpart.
|
| http://dbpedia.org/ontology/wikiPageExternalLink
|
http://disphelper.sourceforge.net/ +
, http://be-sure-soft.com/idispatchcodegenerator/ +
|
| http://dbpedia.org/ontology/wikiPageID
|
1918549
|
| http://dbpedia.org/ontology/wikiPageLength
|
4490
|
| http://dbpedia.org/ontology/wikiPageRevisionID
|
1041540761
|
| http://dbpedia.org/ontology/wikiPageWikiLink
|
http://dbpedia.org/resource/JavaScript +
, http://dbpedia.org/resource/Late_binding +
, http://dbpedia.org/resource/Variant_type_%28COM%29 +
, http://dbpedia.org/resource/Globally_unique_identifier +
, http://dbpedia.org/resource/Component_Object_Model +
, http://dbpedia.org/resource/Category:Object-oriented_programming +
, http://dbpedia.org/resource/Internet_Information_Services +
, http://dbpedia.org/resource/Active_Server_Pages +
, http://dbpedia.org/resource/Run-time_type_information +
, http://dbpedia.org/resource/Category:Microsoft_application_programming_interfaces +
, http://dbpedia.org/resource/String_%28computer_science%29 +
, http://dbpedia.org/resource/Interface_ID +
, http://dbpedia.org/resource/Dynamic_Data_Exchange +
, http://dbpedia.org/resource/Internet_Explorer +
, http://dbpedia.org/resource/Interface_%28computer_science%29 +
, http://dbpedia.org/resource/IUnknown +
, http://dbpedia.org/resource/OLE_Automation +
, http://dbpedia.org/resource/Open-source_model +
|
| http://dbpedia.org/property/wikiPageUsesTemplate
|
http://dbpedia.org/resource/Template:Reflist +
, http://dbpedia.org/resource/Template:More_footnotes +
|
| http://purl.org/dc/terms/subject
|
http://dbpedia.org/resource/Category:Object-oriented_programming +
, http://dbpedia.org/resource/Category:Microsoft_application_programming_interfaces +
|
| http://purl.org/linguistics/gold/hypernym
|
http://dbpedia.org/resource/Interface +
|
| http://www.w3.org/ns/prov#wasDerivedFrom
|
http://en.wikipedia.org/wiki/IDispatch?oldid=1041540761&ns=0 +
|
| http://xmlns.com/foaf/0.1/isPrimaryTopicOf
|
http://en.wikipedia.org/wiki/IDispatch +
|
| owl:sameAs |
http://www.wikidata.org/entity/Q5970136 +
, http://zh.dbpedia.org/resource/IDispatch +
, https://global.dbpedia.org/id/4nbds +
, http://rdf.freebase.com/ns/m.0660x1 +
, http://dbpedia.org/resource/IDispatch +
|
| rdf:type |
http://dbpedia.org/ontology/Software +
|
| rdfs:comment |
IDispatch介面是组件对象模型（COM）中的标准介面，也称自动化（Automa … IDispatch介面是组件对象模型（COM）中的标准介面，也称自动化（Automation）接口，继承自IUnknown，用于讓其他函式使用协议。COM規格書規定COM物件应该是三种接口类型中的至少一种：
* 基于虚表（vtable）的IUnknown的定制接口；
* 分派（dispatch）的IDispatch接口以支持內觀資訊（introspection）。允许客户应用程序在运行时查出COM组件支持哪些属性与方法，即实现了运行期类型信息（RTTI）。客户应用程序编译时不需要知道COM的对象成员。脚本语言如VBS不能使用指针乃至函数指针，只能通过IDispatch接口访问COM组件。这是通过执行IDispatch接口中的Invoke方法。这是一种。与第一种定制接口相比，增加了內觀資訊与invoke的开销。
* dual接口，同时支持上述两种类型的接口增加了內觀資訊与invoke的开销。
* dual接口，同时支持上述两种类型的接口
, IDispatch is the interface that exposes th … IDispatch is the interface that exposes the OLE Automation protocol. Extending IUnknown, it is one of the standard interfaces that can be exposed by COM objects. COM distinguishes between three interface types: custom that are VTABLE-based IUnknown interfaces, dispatch that are IDispatch interfaces supporting introspection, and dual interfaces supporting both types.and dual interfaces supporting both types.
|
| rdfs:label |
IDispatch
|
