PCoIP Session Phases

There are two phases in a PCoIP session:

PCoIP Session-Creation Steps and Actors

The steps indicated below are used and documented in the bundled sample code. Refer to the code for specific function calls, expected return values and error-handling requirements. The example C++ code can be found in the SDK package located here:

PCoIP Core Library Integration

The core library allows an application developer to integrate a PCoIP session directly into an application. The core library facilitates connection to a remote host, decoding PCoIP image data directly into an application supplied frame buffer as well as remoting audio, keyboard and mouse events and supported USB devices.

Passing Customization Parameters to the Session Client

When using the -l option with broker_client_example parameter to automatically pass session information to the session client, you can pass additional session client parameters by enclosing them in double quotes.

What's New in This Release?

Release 24.07 of the Client SDK for Windows includes:

Anyware Software Client for Windows now supports USB webcams when connecting to a Anyware Agent for Windows. USB webcams can now be used while in the remote desktop, including with applications such as Microsoft Teams or Zoom.

For detailed information which models have been tested and the performance metrics associated with these models see here. This knowledge base article also deals steps on how to test and verify other webcam models.

About the Anyware Client SDK for Windows

The Client SDK for Windows does not ship with its own session client binary; it uses the standard Anyware Software Client for Windows binary instead. Therefore, you must first download and install the Anyware client application, and then invoke it from the SDK.

About PCoIP Sessions

Establishing a PCoIP session involves a number of key components, including system actors, PCoIP session phases, and connection brokers as discussed next.

System Actors

There are at least three components that work together to create a PCoIP session:

Manually Bridging USB Devices

If you need to support more than 20 USB devices, or if you expect your users to control which devices can be bridged, they can be manually added by opening the client’s USB Devices menu and enabling them.

Limits on Customization

You may not be able to programmatically modify certain session features due to limitations imposed by the operating systems's user interface.