Meeseeker Handling JSON-RPC Batch - 0.0.9

I added the ability for meeseeker to degrade gracefully if the node does not support json-rpc-batch. This is determined by an error response code 413 (Request Entity Too Large), which will cause meeseeker to retry the original request, but with a maximum request size of 1, instead of the default of 50 defined by steem-ruby.

This should allow meeseeker to work with more nodes, or even a private node, that is not configured with jussi as a reverse proxy.

Typically, meeseeker doesn't need to use json-rpc-batch under normal circumstances. Usually, batched requests would be a solution for when meeseeker falls behind on blocks. But as long as it doesn't fall too far behind, avoiding batched requests shouldn't impact performance.

What Changed ...

There's only one commit for 0.0.9.

Degrade gracefully if the node doesn't support json-rpc-batch a62c98e

This adds a fallback handler that sets the number of requests in a batch to one.

To update your gem:

gem update meeseeker

^{Previous posts:}

• ^{Meeseeker Steem Engine Virtual Transaction Support - 0.0.8}
• ^{Meeseeker Mosly Minor Steem Engine Fixes - 0.0.7}
• ^{Meeseeker Steem Engine Support - 0.0.6}
• ^{Meeseeker Op Timestamps - 0.0.5}
• ^{Meeseeker Witness Schedule Pub/Sub - 0.0.4}
• ^{Meeseeker on Docker}
• ^{Meeseeker Update - 0.0.3pre1}
• ^{I'm Mr. Meeseeks! Look at me!}