Discussion Why we are forced to use the companion API for market data instead of commanders journal?
- Thread starter mLine
- Start date
I think you've kind of answered your own question there. The amount of data needed to download to capture the market data would be quite large when compared to the rest of the entries and if you go down the route creating a different file as you suggest, well, that needs a second system to read the market data which is what we already have.
I've created a utility to read mission data from the journal file for my squad, but sometimes they have difficulty getting it to run because I suspect that occasionally the file is locked while being written to when I want to to read it. I have implemented a retry loop to get around this, but throwing a request at a server and reading the result is a lot easier and neater than reading an active file. I wish we could get all the data from simple web requests but then it is also useful having the historical data sitting on your hard drive without triggering loads a network traffic.
The fact is it is more practical to have certain data recorded locally and other data available on demand and so far, I think they have it about right.
I've created a utility to read mission data from the journal file for my squad, but sometimes they have difficulty getting it to run because I suspect that occasionally the file is locked while being written to when I want to to read it. I have implemented a retry loop to get around this, but throwing a request at a server and reading the result is a lot easier and neater than reading an active file. I wish we could get all the data from simple web requests but then it is also useful having the historical data sitting on your hard drive without triggering loads a network traffic.
The fact is it is more practical to have certain data recorded locally and other data available on demand and so far, I think they have it about right.
the only two issues with the market data is see,
ist he requirement of external tools to store and review the data from a station, even when i am able to "buy" said data on the galmap to show me fancy colored arcs.
and the other one is... i have to reveal my personal FDEV account data + password to access that data?? for real?
ist he requirement of external tools to store and review the data from a station, even when i am able to "buy" said data on the galmap to show me fancy colored arcs.
and the other one is... i have to reveal my personal FDEV account data + password to access that data?? for real?
Maybe i dont get your point... if ED write the market data in a journal file at station-docking, you don't have to download any data. This mechanism is still there (take a look at the "Docked" event) and only needs small modifications.
If you want to read from a file used by another process use a file-system-watcher-mechanism and open this file for read-only.
3th party apps still use this mechanism to read the cAPI if the event "Docked" occurs in commander journal.