For those who are (still) using Citrix Application Streaming, this article from the CitrixKB describes the communication process that occurs when a user requests a streamed application from XenApp.
- A user clicks a published application icon for an application configured for streaming. The application launch request is relayed to Web Interface.

- Web Interface contacts the XenApp server to obtain the information required to run the application.

- Web Interface creates a .RAD file based on the information obtained from the XenApp server and provides for the RadeRun utility, (RADERUN.EXE), which can be in either of two of the following locations.
- Located on the client device, if the published application is being streamed to the desktop of the client device
- Located on the XenApp server, if the published application is being streamed to a server

- The RADERUN utility passes the .RAD file to the Citrix Streaming Service (RADESVC), which creates an isolation environment and downloads the application profile from the server.

- The Citrix Streaming Service opens the application executable according to the instructions included in the application profile and runs the executable inside the isolation space

- Additional application files are downloaded from the server as needed during normal application usage.

Source: CTX128917

Why do you write “still” in your article? Is there a alternative to application streaming?
Hi Victor,
I believe ThinApp and Microsoft App-V are way more solid (sorry Citrix!)