I would like to implement the following arrangement: published app communicates via TCP/IP with app running on the local client.
The reason for doing this is I would like the published app to be able to access a piece of the local hardware that isn't available under USB redirection or other means. I have both apps built and they work well standalone on the local PC.
What will be the local app is simply a service built in .NET/WCF. What will be the published app talks to the local app via http/TCP/IP connection. The local app(service) is listening for a connection from the published app. Published app initiates communication with the local app.
Is this possible under Xenapp? And if so to the published app what is the IP address of the local host where the local app is running? When the "published" app and the local app "service" run on a physical machine(no Xenapp at all) the "published" app simply calls into http:localhost:.
Is there a concept of "localhost" representing the local machine to the published app? Or do we have to use the actual physical IP address on the network to be able to communicate between the published app and the local app?