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
{{ message }}
Repository navigation
Supporting platform that has no sun.misc.Unsafe #194
We have got an report that the current msgpack-core doesn't work in GAE. MessageBuffer implementation is designed to achieve the best performance for accessing memory through sun.misc.Unsafe. But Unsafe is not avilable in GAE.
Loading sun.misc.Unsafe might fail in GAE.
Simply referencing it in the code (in import statement or field declaration) may have no problem; @xuwei-k reported the error log when using msgpack-core-0.7.0-p5 in https://gist.github.com/xuwei-k/31f9c9256439af0c3272 (error occurred after Unsafe u; statement)
We NEVER create any interface for MessageBuffer because it changes invokevirtual calls to invokeinterface and deteriorates the performance. And also having two or more classes that implement MessageBuffer methods generates TypeProfile. It makes each method call 2x slower.
I have succeeded in using MessageBufferU, which does not rely on Unsafe class. Another problem is there is no java.nio.DirectByteBuffer class in GAE. I'm seeking a workaround.
Activity
[-]Supporting platform that doesn't have no sun.misc.Unsafe[/-][+]Supporting platform that has no sun.misc.Unsafe[/+]xerial commentedon Feb 10, 2015
I'm working on this task on https://github.com/xerial/msgpack-java/tree/v07-no-unsafe branch.
I have succeeded in using MessageBufferU, which does not rely on Unsafe class. Another problem is there is no java.nio.DirectByteBuffer class in GAE. I'm seeking a workaround.
xerial commentedon Feb 16, 2015
Just deployed 0.7.0-p7, which supports GAE.
oza commentedon Feb 16, 2015
Good job!