05-21 Set average RSSI in redis

Today there were no big issues, so this post will be short. The incoming measurements as stored in a redis list, where the measurement's server_addr field is the key. It trims the queue length to 100 measurements, which should be fine since the complexity is only O(1) if never more than one value is removed. There are no more failed requests due to long processing time, since no queries are done on the db to check if a server exists or to get the server id (for the measurement.server_id foreign key). The server address is directly the unique foreign key reference.

The next question is how to decouple the measurement storing mechanism from the redis store event. An event listener is the first thing that comes to mind, but perhaps it should run as a queued event listener to handle interrupts etc. I am not sure how concurrency is dealt with.