Yeah, now I've worked out the EDDN thing the data is exploding. I'll move within a few days. But also looking at compression.
As a side note, since I kinda prodded the topic in the first place... I started adjusting transfers.py to handle gzip encoding and ran into a bit of fun I'd forgotten about, at least with my test server (nginx). With content-encoding: gzip --> no content-length header. Fun fun.
Also an update on this:
Well, I'm nowhere near 'usable' with it (mostly because it's the first time I've dove into python), but I'm poking at a bottle.py based front end for TD to be used with something like overwolf or the steam overlay browser from a user's local system. I ran across a php-based tool someone threw together with overwolf in mind, but it just gives a blank entry for command line arguments, then runs trade.py with that. I started in on my little toy to, hopefully, a) keep the database loaded, b) use the internals of yours directly from python, and c) avoid having to run a separate webserver.
I traded sleep for a deeper understanding of TD's internals. My little toy needs a proper frontend attached, backend and frontend refactored out to be a bit more separate (and modular), and probably a LOT of api cleanup (it's a bit random on naming things, mostly pulling wholesale from trade.py command line arguments), but it's working to take input and spit out json for most things. Run's going to take a bit of work for output handling, but it is moving along. I'll get it put up in a git repo once I've separated things slightly. I'm really, incredibly, impressed with how clean TDs code is, by the way. Once I'd wrapped my head around it, I realized how incredibly trivial it is to use