1. Today's data is not available via CREST
2. Data older than 14 months can't be retrieved from the API, but is commonly found in EMDR history messages
3. No scraping necessary, no 10 connections/sec limitp
I'd propose a filtering mechanism for EMDR, which discards market data points that can be retrieved from CREST and only lets current (age < 24h) or datapoints older than 14 months pass the filter. This also would reduce traffic enormously.
I'm currently preparing version 2.0 of node43 - the NodeJS based consumer of Element43. As order/history messages hit the consumer, each region/type combination in that message will trigger a CREST history API call which only gets called once every 24h. If that same region/type pair hits the consumer 3 minutes later, another CREST update would not be scheduled. With the CREST history API comes another problem: you'd have to scrape the API if you'd like to get the entire market. This won't make neither CCP nor us 3rd party devs happy. So the idea is that node43 will submit the data collected from CREST directly to EMDR in UUDIF format. Since the API calls only occur for active items (region/type pairs that get sent to EMDR indicate activitiy most of the time, as the upload is triggered by people looking at items in the in-game market) and only once every 24h, redundancy of the EMDR history feed would be greatly reduced.
This would mean:
1. Reduced redundancy and traffic of the EMDR history feed
2. Current and very old records will still be available
3. No need to rewrite existing applications, as node43 uploads official data the same way players do
4. Official data available via EMDR -> reduced CREST server load, no scraping necessary
5. EMDR users could filter for node43's ip hash so they can decide to only consume official data
6. Reduces load and complexity for other EMDR consumers
1. Today's data is not available via CREST
2. Data older than 14 months can't be retrieved from the API, but is commonly found in EMDR history messages
3. No scraping necessary, no 10 connections/sec limitp
Seems like current order data (not history) would be better for this, though. You'll get all kinds of order data of varying ages on a given day.
--
You received this message because you are subscribed to the Google Groups "EVE Market Data Relay" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eve-emdr+u...@googlegroups.com.
To post to this group, send email to eve-...@googlegroups.com.
Visit this group at http://groups.google.com/group/eve-emdr.
For more options, visit https://groups.google.com/d/optout.