|
June 23, 2014, 05:35:05 PM |
|
Well, if you query large chunks of raw data and process it yourself, no wonder that you get faster response times...
However in your example you end up with a raw encoded transaction, in the "obvious" case you have a nicely decoded transaction in JSON format... if I needed high speeds + python I'd rather use something like pynode or let Armory do the parsing for me, if I were just trying out stuff, the few GB or RAM or SSD space for the index are much cheaper than me writing a raw transaction decoder.
|