moooonk commented on issue #2818: URL: https://github.com/apache/fory/issues/2818#issuecomment-3437961889
@chaokunyang Thank you for your reply. Regarding the documentation, I will provide some update later. As for name registration, I fully understand that the design of the registration ID is for the purpose of data header compression. I have reviewed the source code, and it is feasible to modify the registration to use name-based registration. In general, using shorter names for registration may yield slightly worse performance compared to using registration IDs, but it performs better than decoding with full class names in non-registration mode. I believe this is a completely viable solution, and I appreciate your suggestion. An additional point I’d like to add: Using registration IDs is the default recommendation in most documentation. However, based on the current situation, if improper registration leads to deserialization errors, it may cause silent failures rather than throwing an exception to alert the user early in the deserialization process. If such a situation occurs, it would be very difficult for users to realize that runtime type errors are caused by improper registration. That said, I’m not sure whether the current serialized data includes any mechanism to support early validation of registration ID errors during serialization—it seems there isn’t. Do you have any advice on this? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
