Skip to content

Latest commit

 

History

History
79 lines (63 loc) · 2.99 KB

nn-objidlbase-ipipelong.md

File metadata and controls

79 lines (63 loc) · 2.99 KB
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.IPipeLong
IPipeLong (objidlbase.h)
The IPipeLong (objidlbase.h) interface transfers data of the long integer type (which is 32 bits wide).
IPipeLong
IPipeLong interface [COM]
IPipeLong interface [COM]
described
_com_ipipelong
com.ipipelong
objidlbase/IPipeLong
com\ipipelong.htm
com
c1b4d3b3-e1bf-4441-8cea-b667b82c4c27
08/15/2022
IPipeLong, IPipeLong interface [COM], IPipeLong interface [COM],described, _com_ipipelong, com.ipipelong, objidlbase/IPipeLong
objidlbase.h
ObjIdl.h
Windows
Windows 2000 Professional [desktop apps only]
Windows 2000 Server [desktop apps only]
ObjIdl.idl
Windows
19H1
IPipeLong
objidlbase/IPipeLong
c++
APIRef
kbSyntax
COM
objidlbase.h
IPipeLong

IPipeLong interface

-description

Transfers data of the long integer type (which is 32 bits wide).

-inheritance

The IPipeLong interface inherits from the IUnknown interface. IPipeLong also has these types of members:

-remarks

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.
For more information, see Pipes in the RPC documentation.

-see-also

IPipeByte

IPipeDouble