Wayne Xu
Wayne Xu
version info: msm : 2.1.1 kryo : 4.0.0 kryo-serializers : 0.41 minlog : 1.2 objenesis: 2.2 reflectasm: 1.11.3 asm: 5.0.4 setting: ```xml ```
Thanks for the reply! Now we get hashcode by the attributesData(the attributes has been serialized). If sort attributes before computing the hashcode , we'll get hashcode by the attributes has...
Thank you very much! I got the same hashcode when the attributes been sorted.
You are right, in `getAttributesFiltered` there's no real need for sorted attributes and `TreeMap` is safer than `ConcurrentHashMap `. Add a new method `int getHashCodeByAttributes(ConcurrentMap attributes)` when get hashcode is...
I meant i don't know how to get hashcode by sorted attributes. Can you give me some advice?
ConcurrentMap is be required in serializeAttributes method, if the attributes change to Map , serializeAttributes method is need to modify?
This is my worry. Are there any other solutions?
There is a test case: ```java public class MapSerializerTest { private Kryo _kryo; @BeforeTest public void setUp() throws Exception { _kryo = new Kryo(); MapSerializer.registerSerializers(_kryo); } @Test public void testDeserialize()...
The same data serialized differently. Maybe it's because of that the deserialized data is not deep equals with the original data. When I run this test: ```java @Test public void...
Yes, this not happen with `ConcurrentSkipListMap`, but , we must to change more... So, can we keep the same order to put attributes into `ConcurrentHashMap`? When we put the attributes...