bindata VS EventMachine

I recently ditched bindata for a self written solution because I couldn't figure out why exactly it leaks memory. According to count objects it creates a shit ton of classes if you read a lot of data and idk why

"Writing an entire custom program" is the best way. Ruby has a nice package called bindata (https://github.com/dmendel/bindata) that works well for this purpose.

For example, I enjoy sim racing, and some of my games provide a network API for things like telemetry data. So I wrote a simple telemetry logger that I use to gather data, which I then mess around with using R Studio. Ruby worked exceptionally well for this because of a cool little library called BinData.

These projects always remind me of binary formats. I've used bindata to work with binary formats coming from UDP streams over a network, and it's very handy to have a layer that encapsulates your expectations about the data you're receiving, combined with an exception handling apparatus.

You could also use something like EventMachine (In ruby), Twisted (Python), Node (JS) or ReactPHP (for PHP) that will use the language and turn it into a web application server, and then you'll have only one long running process that handle all your requests with shared memory. You could even use something more fancy like RoadRunner in the case of PHP.

Maybe check out EventMachine. You can roll your own using sockets if you don't want to use a library.

EventMachine