Serialization can be negotiated using id to improve performance.

[chickenlj]

When user set serialization="hessian2", use corresponding id internally.

[diecui1202]

@chickenlj Could u pls. describe it with more details?

[chickenlj]

Firstly, this is a performance tuning task. Dubbo internally have a name-id mapping for each serialization implementation, for example,

• hessian - 2
• fastjson - 6

What I suggest is, use serialization id instead of name whenever we need to negotiate serialization between Provider and Consumer.

1. the URL registered to the registry.
2. payload on the wire during an RPC.

[chickenlj]

At present, I think it's no big deal whether we are using serialization name or id. Considering the tasks we have on hand, we can tune it later.