Well, this is what I was talking about with pipes. Pipes are basically sockets (like network connections) between applications running on a machine, and you can send and recieve data through them. I was thinking if DB sent it's stats in JSON format like so:
{ "population":"12381412", "cyclespersec":"50"}
down the pipe, then DBIM could just send that straight up to the server, which would process it server side. What this means is that we can make one modification to DB (adding pipe support + json), create a new DBIM and server script and then have all the functionality we currently have with the caveats that:
a) We wouldn't need to update DBIM ever again (unless a bug appeared or another overhaul was needed)
b) Adding new stats to track would be a simple case of adding the stat in DB's JSON sending bit and updating the server script to process the new stat, instead of an update to all three elements (DB, DBIM, server script)
Also, this potentially allows for complete control of the DBIM application from DB's interface if we want to go down that route.