| UID | title | description | helpviewer_keywords | old-location | tech.root | ms.assetid | ms.date | ms.keywords | req.header | req.include-header | req.target-type | req.target-min-winverclnt | req.target-min-winversvr | req.kmdf-ver | req.umdf-ver | req.ddi-compliance | req.unicode-ansi | req.idl | req.max-support | req.namespace | req.assembly | req.type-library | req.lib | req.dll | req.irql | targetos | req.typenames | req.redist | ms.custom | f1_keywords | dev_langs | topic_type | api_type | api_location | api_name | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NN:objidlbase.IPipeDouble |
IPipeDouble (objidlbase.h) |
The IPipeDouble (objidlbase.h) interface transfers data of the double type (which is 64 bits wide). |
|
com\ipipedouble.htm |
com |
434d0e0e-55a0-4a08-bc63-ebca4b2bdcca |
08/15/2022 |
IPipeDouble, IPipeDouble interface [COM], IPipeDouble interface [COM],described, _com_ipipedouble, com.ipipedouble, objidlbase/IPipeDouble |
objidlbase.h |
ObjIdl.h |
Windows |
Windows 2000 Professional [desktop apps only] |
Windows 2000 Server [desktop apps only] |
ObjIdl.idl |
Windows |
19H1 |
|
|
|
|
|
|
Transfers data of the double type (which is 64 bits wide).
The IPipeDouble interface inherits from the IUnknown interface. IPipeDouble also has these types of members:
The IPipeByte, IPipeDouble, and IPipeLong interfaces are similar to the standard DCE/RPC pipes. However, the COM implementation of pipes offers more flexibility. With the COM implementation, the basic idea is that the pipe is simply another interface with two methods: Pull and Push. This results in three main benefits:
- A COM pipe is another interface, so it can be received as an out parameter from a method call and then either Pull or Push can be called.
- There are no restrictions on when to call the Pull and Push methods, so a pipe is in reality bidirectional.
- Pipes are interfaces, so the method calls can be asynchronous and follow those rules.