@kerry.lytle The official position is that the standalone proxy for windows has not been supported for years now. The standalone proxy for mac is however still supported as there is no native Eikon for Mac - of course Workspace does have a native mac version which has a built-in proxy and no longer requires the standalone proxy.

Is there a particular reason the user does not want to move to a supported workflow with no change to codebase?

@kerry.lytle There is no need for the client to use the standalone proxy as the proxy was built into Eikon quite some time ago. The standalone proxy is legacy and no development work has been done since May 2019. If he is using 4.0.52 he should use the inbuilt proxy as he will have access to all the latest features such as Streaming Real-Time and also all the new services by using the RDP libraries (new enhanced timeseries history service, Search, Symbology and many more are being added all the time).

A further advantage of not using the standalone proxy is stability and also the fact that he can use Eikon and the proxy at the same time (which the standalone does not allow). He should upgrade to the latest Eikon libraries and follow the Quick Start Guide. Examples of how to use the new feature such as streaming are available here.

To use the RDP libraries he can find out more here - but perhaps the easiest way to see how the RDP libraries work is to open the CODEBOOK app (type CODEBOOK into Eikon search bar). This is a hosted scripting environment and it has full examples of using both Eikon Data APIs and also RDP libraries with a desktop session. The Eikon Data APIs have been fully integrated into the RDP libraries and can be accessed using the samples there - see screenshots below:

I hope this can help.

Thank you Jason. But my question remains unanswered.

Is the old Eikon API Proxy application (for Windows) still supported or not?

Many thanks!