Services. Are they up and running yet? - page 7

 
fxsaber:

I don't know why feedback is needed yet. But transferring data via again Resources to Service is not a problem.

The point of the service is to hang in the background and handle some batch tasks. If it is something of regular cycle - like start once and forget about it - it is one thing. But what if it is periodical? How to transfer a new task to the service? How to launch a service from MQL? Resources, files and other workarounds are clear, but leave much to be desired.

 
Stanislav Korotky:

The essence of the service is to hang in the background and handle some batch tasks. If it's something of a constant cycle - like run once and forget about it - that's one thing. But what if it is recurring? How to transfer a new task to the service? How to launch a service from MQL? Resources, files and other workarounds are clear, but leave much to be desired.

90% of services are tuned for custom builds. So that there are custom symbols with stack and stuff. That's why not only receiving but also sending data was not even considered. A kind of self-sufficient programs, which are distinguished by the property that they automatically start with the Terminal.

 
Stanislav Korotky:

The essence of the service is to hang in the background and handle some batch tasks. If it's something of a constant cycle - like run once and forget about it - that's one thing. But what if it is recurring? How to transfer a new task to the service? How to launch a service from MQL? Resources, files and other workarounds are clear, but leave much to be desired.

Resources provide a great way to exchange information between programs. You just need to know how to work with them. At first I thought that MQL didn't have any voluminous shared application memory. It turns out that there is, but in a somewhat unusual form - in the form of resources.

 
fxsaber:

The services are 90% customised for third party feeds.

This is narrow and diminishes the value of the services, IMHO

 
Stanislav Korotky:

This is narrow and diminishes the value of the services, IMHO

That's the vision of the developers. Vaughn, with custom ones trying to break through

 

Is there a single case where it is more convenient to use than an EA or script?

 
TheXpert:

Is there a single case where it is more convenient to use than an EA or script?

Current formulaic synthetics are implemented in the form of hidden but same Services. That's the convenience of it.

 
TheXpert:

Is there a single case where it is more convenient to use them than an EA or a script?

it doesn't make sense, I can't think of it myself

positioning them as 90% feeds, but not being able to access different accounts from one copy of the terminal at the same time

then what are the feeds? if almost every 2nd feed now has mt5, be it a stock exchange or a DTs
 
Maxim Dmitrievsky:

then what are the feeds? if almost any feed now has mt5, whether it's an exchange or a DT

If you think like that, then there is no need for formulaic synthetics either.

 
fxsaber:

If you think about it that way, then there's no need for formulaic synthetics either.

so how can you make feeds that are not focused on your own platform when most feeds are available through it

just open up the possibility of accessing other accounts from the services and they become perfectly adequate