![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
supplemented the question.
what event, and how will you retrieve data when it occurs?
no, you don't need to bash the websocket, it's a websocket;) once you subscribe to the right tools, all you need to do is read the data stream...
there are a couple of javascripts in this widget, they communicate with the server via this same websocket... if only they could be decrypted, everything would be clearer...
We pull data from table cells - they have names (identifiers).
Forum on trading, automated trading systems and trading strategy testing
Getting price feed through WebSocket in C#.
Yuriy Asaulenko, 2016.05.18 18:49
Event - change of price in widget table in browser. I can't go into more detail as there are other tasks at the moment.no, you don't need to bang the websocket, it's a websocket;) once you subscribe to the right tools, all you have to do is read the data stream...
there are a couple of javascripts in this widget, they communicate with the server via this same websocket... If they could be decrypted, everything would be clearer.
the problem is that the standard.netclass doesn't have a method to subscribe to https://msdn.microsoft.com/ru-ru/library/system.net.websockets.websocket(v=vs.110).aspx web socket events, it can only be used for pounding :)
i.e. either asp.net should have suitable methods, or some other way
or there's no problem, and I just haven't figured it out yet
in a nutshell, a websocket is a modification of a simple JS socket to work through web browsers. the connection is established at the beginning of the session and lasts until the page is closed...
Communication with the server is another issue, it uses their own json protocol, if I understand it correctly. The question is to dig out the subscription requests from the html/JavaScript/json itself...
then create a websocket connection, shove subscription request into the socket and read the thread in the loop...
eh, I was wondering where I could find the time...
by the way clientwebsocket is closer to the truth, that's something like thishttp://codereview.stackexchange.com/questions/41591/websockets-client-code-and-making-it-production-ready
in a nutshell, a websocket is a modification of a simple JS socket to work through web browsers. the connection is established at the beginning of the session and lasts until the page is closed...
Communication with the server is another issue, it uses their own json protocol, if I understand it correctly. The question is to dig out the subscription requests from the html/JavaScript/json itself...
then create a websocket connection, shove a subscription request into the socket and read the thread in the loop...
eh, I was wondering where I could find the time...
by the way, clientwebsocket is closer to the truth, something like this http://codereview.stackexchange.com/questions/41591/websockets-client-code-and-making-it-production-ready
Well here are all the headers to the keys to connect to it, if I understand it correctly. I've downloaded samples, I'm trying to figure them out :) the problem is aggravated by almost complete lack of C# programming skills, come on, help me out :))
The subscription request seems to be of this kind
It is called parsing!
What's your point? Well, you can say words too, and a lot of them. :) You probably get paid, too, right? Parsing? - well, there are gaps in the terminology. :)
Look at browser object model and DHTML and you'll see which events need to be intercepted. If from page in browser, how to do it directly from C#, I don't know. I don't know - I haven't tried it. :)
Ps Looked that there is parsing - parsing of site information. So we are talking about different things. Hence correctly said - fiddler parsing is not necessary.