You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drogon uses jsoncpp as its JSON handler library by default.
Switching jsoncpp into nlohman or rapidjson may improve its performance, but it could break Drogon's backward compatibility since Drogon provides jsoncpp's JSON object(JSON::Value) from requests or responses.
You can specialize from_request or to_response template classes to switch Drogon's Json handler to another, but I guess benchmarks like above will not run tests that way.
Also, there's a discussion regarding Drogon 2.0 on switching Drogon's JSON library to another.
Please continue the discussion on the already mentioned discussion (#682) where the same topic is discussed. I will close this discussion in order to reduce duplicates.
When I was comparing Drogon with other in Json-Sterilization I was not understanding how Drogon can rank less in it
What might be cause of it and will it be improved in feature
since Drogon is so strong in other feature then why can't it be in Json-Sterilization.
The text was updated successfully, but these errors were encountered: