Simple Ruby EMDR Client

This is a very simple client for connecting to the EVE Market Data Relay network. This is a ZeroMQ network of user submitted information about the player-driven market in EVE Online. The messages received are in the Unified Uploader Data Interchange Format as specified by EVE Central.

Players voluntarily upload market data as they are playing the game. When a player makes a market query in game, that data is cached locally on their computer. This cache can be parsed and uploaded through various clients.

This is "drinking from the fire hose". I have seen the messages come in at over 20 a second. There are two types of messages: orders and history. The contents of the message depend on its type.

For order messages, you'll have rowsets with a row for each order on the market. For high volume items, that could be hundreds of rows. For low volume items, it may only be a few.

For history messages, you'll have a rowset with a row for each day. How many days depend on the date range the player specified in the client. It may only be a week's history, or could be a year's history.

You should know what you want to do with this data and only keep the pieces you need. Keeping it all in a format that's easy to search is hard and will take a lot of disk space.

Installation

While this project was initialized using bundle gem, it's not technically a gem. It's not designed to be included into another project. It's just a simple, working EMDR client.

To install, clone this code locally and then run bundle install. Because this project is laid out like a gem, the dependencies are specified in the emdr.gemspec; primarily Celluloid ZMQ.

Usage

Then you should simply be able to run the client like so:

bin/emdr-client.rb

This will connect to the EMDR and puts out a notice about every message received:

Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type orders from 2013-11-12T16:05:08+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type orders from 2013-11-12T16:05:08+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type orders from 2013-11-12T16:05:08+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:08+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:08+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type orders from 2013-11-12T16:05:08+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:09+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type orders from 2013-11-12T16:05:09+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:09+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:10+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:10+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:10+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type orders from 2013-11-12T16:05:10+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:10+00:00
Message from EVEMon.MarketUnifiedUploader/1.8.3.4116 of type history from 2013-11-12T16:05:10+00:00

It will also puts out the rate at which messages are being received every 30 seconds:

Receiving 9.766227349206408 messages/sec

Go Faster!

I've commented out printing the message receipt. Turns out printing to the terminal is very time consuming. As it stands now, it's basically just a measure of how fast Celluloid can receive messages from ZeroMQ.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request