MetaQuotes VPS service specification - page 2

 
Alain Verleyen:
Bugs doesn't necessarily result in errors in the log. Debug and fix your code.


heheh laugh laugh you won't get no penny from - if i make it work ! :-)

Eleni Anna Branou:

As Alain said, the error must be in your code, not in the VPS.

i'm thinking of an OnTrade/OnTradeTransaction() to filter any request, likely it should block any new req before previous one's response. 

Yet I swear I'm not in Async mode. 

 
Icham Aidibe:

That one for example, there's no log entry saying it has been closed. Likely modify orders aren't all handled by the server even if it's 69ms and in test it seems able to support up to 500-1000ms without no errors : 

when i say no error it's no error ... believe me pls i won't repaste the screenshot everytime :/ 

Btw to close many positions, is there a better way than looping thru ? 

It doesn't say the position was close, it's says it's too close to market.

A sell is closed at ask price, so your SL must be >= ask price + stoplevel.

 
Alain Verleyen:

It doesn't say the position was close, it's says it's too close to market.

A sell is closed at ask price, so your SL must be >= ask price + stoplevel.

That's why I want likely a request firewall : 

  • async mode false : req req req ----> req - confirmation or not - req - confirmation or not - req - confirmation or not (server side, queue)
  • async mode true : req req req -----> req confirm or not - req confirm or not - req missed or not
  • firewall : req - wait for confirmation - req - wait for confirm - request wait for confirmation (client side, queue)
Is it right ? I'm not confusing them ? Just that will be enough to clean the log from this asynchronized req, because the new request you highlighted is made when the price has changed and before the server response - i think
 
Icham Aidibe:

That's why I want likely a request firewall : 

  • async mode false : req req req ----> req - confirmation or not - req - confirmation or not - req - confirmation or not (server side, queue)
  • async mode true : req req req -----> req confirm or not - req confirm or not - req missed or not
  • firewall : req - wait for confirmation - req - wait for confirm - request wait for confirmation (client side, queue)
Is it right ? I'm not confusing them ? Just that will be enough to clean the log from this asynchronized req, because the new request you highlighted is made when the price has changed and before the server response - i think
Maybe. I have no idea what is your code.