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
/**
*
* Preregister a class (use at init time). This avoids having to write class names.
* Its a very simple and effective optimization (frequently > 2 times faster for small objects).
*
* Read and write side need to have classes preregistered in the exact same order.
*
* The list does not have to be complete. Just add your most frequently serialized classes here
* to get significant gains in speed and smaller serialized representation size.
*
*/
Let's say on the write side A.class is registered. How is deserialization going to behave in the below cases
On the read side A.class is not registered and instead some other class, B.class is registered. Will the read side break in this case during deserialization?
On the read side no class is registered. Will read side work?
On the read side FST is not used and JDK serialization is used. Will the read side break in this case?
The text was updated successfully, but these errors were encountered:
Hi
The javadoc of registerClass states like below
Let's say on the write side
A.class
is registered. How is deserialization going to behave in the below casesA.class
is not registered and instead some other class,B.class
is registered. Will the read side break in this case during deserialization?The text was updated successfully, but these errors were encountered: