I have the following setting
- A jQuery site (not exactly one page, but not far from it) that uses
- ASP.NET MVC website as a backend that connects (via net.tcp or net.pipe) to
- A stand-alone WCF service that manages and connects to
- Lots of high latency external services.
Therefore, when the client clicks the button, a request is sent to MVC, which redirects it to WCF, which aggregates it from external services, and everything is fine and dandy.
The problem with which I do not seem to be enveloping is communication in a different way, i.e. when one of the external services is disabled, the easiest and most elegant way to inform the client (browser)?
This means that the service must somehow inform the mvc site, which must somehow tell the client that the external service is disabled.
Additionally: the external service will have high availability, so the "go offline" scenario will be rarely used, and, accordingly, I am looking for a solution that does not conduct an extensive survey of the server.
Sweko
source share