Elliot.

@sgramkumar please work with @mtrippled and @seelabs on this

note: It may be possible for fetchNodeNT (and the sync cache) to go away with the introduction of FLRv2

- awaiting review by @ximinez (or suggestion of alternate reviewer)

@Bronek - John's request would be a good use for the `Context of Change` section of the PR template :) ``` ### Context of Change ```

@Bronek - any preference on whether this goes in 2.1 or 2.2? Given it is a refactor, I'm not sure if there is some urgency to getting it merged/released.

Note: Protocol message compression support was added in https://github.com/XRPLF/rippled/pull/3287 Ping: @gregtatcam @nbougalis @seelabs @HowardHinnant

> is a stats available on the compression adaption rate? @xzhaous could you check into this?

note: link compression is documented here - https://xrpl.org/enable-link-compression.html but it is not mentioned in rippled-example.cfg - https://github.com/XRPLF/rippled/blob/develop/cfg/rippled-example.cfg

@ckeshava - can you look at the code (and if possible, write a unit test) to confirm that even after the change in this PR, compression can still be fully...

Internal tracker: RPFC-108