devjeonghwan

3 ms·

1. 1.▲
   by devjeonghwan 5y ago

   "Read/write" method of "Input/OutputStream" are not synchronized. but "ByteArrayInput/OutputStream" are synchronized methods. Old version opack call "read/write" method frequently,
2. 2.▲
   by devjeonghwan 5y ago

   https://github.com/realtimetech-solution/opack/commit/ba9309... Here is more detail of optimize code commit
3. 3.▲
   by devjeonghwan 5y ago

   My project took 2306 milliseconds to perform specific performance tests before JVM 15. But, JVM 15(or higher) took 24248 milliseconds. I've heard that this issue is related to "JEP 374". (It's a matter of disabling biase
4. 4.▲
   Interesting example of how “JEP 374” affects performance(github.com)

   4 points by devjeonghwan 5y ago|5 comments
5. 5.▲
   by devjeonghwan 5y ago

   Thank you for comment. I know the vulnerability that you said. i want this library to be safe, so i added data layer(the named OpackValue/OpackArray etc..) for blocking remote code execution.
6. 6.▲
   Fast Java Object JSON/Bytes serialization and deserialization library(github.com)

   5 points by devjeonghwan 5y ago|2 comments