Automatic detection of 'remote' mode ?
/?remote=true option on starting application causes all 3rd party js libraries ( angularjs, d3, jquery etc etc) to get loaded from cloudflare cdns; rather than from the EMIS server.
Whether this is quicker depends on your location wrt these two servers. At one extreme, a user connecting to an EMIS server in RMI from another country will do better to use cloudflare; but a user on the same LAN as the EMIS server is better without remote option. Users in FSM in a different state to the server may well do better with remote, but that could be dependent on how their internet connection is actually routed.
Perhaps we can establish some rules? ie allow some IP masks to be specified in web.config , and determine transparently whether to use remote based on these rules.
As a related issue we would want to be able to turn off remote if it was applied automatically ( for testing?) , so support options
/?remote use remote
/?remote=true use remote
/?remote=false don't use remote
Comments (3)
-
reporter -
reporter - changed status to resolved
feat(remoting):support configuration of addresses to use remoting in web.config
Resolves
#669→ <<cset b127c9bfbfc9>>
-
reporter - Log in to comment
As well as support ?remote (ie valueless query string parameter), also support via AppSetting in web.config: