[Discussion] How about used for HTTP json body?

[laglangyue]

The HTTP body is usually not very large, below 500k, and I think it is very suitable for static symbol tables. But SMAZ is too simple, and the support is actually not good.
HTTP bodies typically have the following characteristics
(1) some key word : "code", "data", http, "msg"," "message", "uuid", "id"
(2) some appKey or appSecret: maybe uuid for appkey, sha, aec, des and so on.

Perhaps FSST can be further optimized for this scenario, especially in the data compression scenarios of HTTP and RPC

I am studying a paper and I do not know C++. I am proficient in Rust. In fact, I am a Java programmer.

Do you think there are any further optimizations in this direction？

[laglangyue]

The current Pekko HTTP and Pekko GRPC projects both use GRPC, which typically has extremely poor performance