In Detail – VMware’s Blast Extreme Protocol
If you are using VMware Horizon/View for VDI, publishing applications and/or Hosted Shared Desktops you have the choice between three protocols: PCoIP, RDP and Blast Extreme, with RDP basically being the fallback protocol when all else fails. Here it’s important to note that Blast has been around for some time in the form of a HTML5 client used through HMTL5 compatible web browsers — available as of VMware Horizon View 5.2 Feature Pack 1. It is the ‘Extreme’ part that is (still relatively) new.
As mentioned, Blast has been around for a couple of years now (since 2013) and so it is no surprise that Blast Extreme builds upon the existing (and best) capabilities of the (older) HTML5 Blast protocol. Once the Horizon View (native) clients have been updated (need to be 4.x at a minimum) enabling support for the Blast Extreme protocol, Administrators can configure one or multiple desktop pools to make use of Blast Extreme or to allow users to change the protocol within their clients themselves (something I would avoid personally, but it’s optional).
The (new) Horizon View client consist out of three specific agent side Blast Extreme components:
- The VMware Blast service (VMBlastS.exe) manages user sessions, proxies incoming TCP connections, and prepares the Blast Worker process
- The Blast Worker process (VMBlastW.exe) captures the screen and handles everything within the session
- If you use UDP, the Blast Proxy process (VMBlastP.exe) brokers UDP connections
Read the entire article here, In detail — VMware’s Blast Extreme protocol
via Bas van Kaam at basvankaam.com