I have requested in a separate post, a description of the Remote Run environment,
and the various techniques or "best practices" which users should develop.
viewtopic.php?f=65&t=50076I hope that Dukascopy will define the services which we can expect with a Remote Run
Strategy, so that we can better understand what we'll need to provide.
One example is communication outside of the Remote Server environment.
As posted in this thread, the IEngine.broadcast(...) is one fundamental method
of communicating among instances of strategies WITHIN A SINGLE ACCOUNT.
As for other forms, such as socket, common file folders, etc., they are mostly
impossible since the code is "sandboxed".
However, once again, if Dukascopy would document this very clearly then
users would understand what features we'll need to develop, and what features
are available in the Remote environment.
I'm currently developing around the IEngine.broadcast mechanism, for inter-Strategy
communication but that involves writing application specific communication
mechanisms, as has been noted earlier in this thread.
Strictly temporary files can be written by a Strategy instance, but these files
will be lost if there is any restart of the Strategy. These limitations need to be
clearly understood by developers, and "best practices" described.
HyperScalper