For more convinient to use the serial package will be nise when library generate code for some type to generate code for all types of fields of this class.

Example: I have class

class MyDto {
        private BigDecimal decimal;
    }

and 2 JVMs between which will be data exchange. (First - serialize, second - deserialize)

Even if I preregister this class on both JVM like

Repository.preload(MyDto.class);

second jvm will not be able to deserialize a data because there is no a serializer for BigDecimal. I know that we can request a schema but it's no needed here we have one already.

As in the title. We noticed that if the server returns some extra whitespace for transfer-encoding header this condition isn't met.

  if (method != Request.METHOD_HEAD && mayHaveBody(response.getStatus())) {
                if ("chunked".equalsIgnoreCase(response.getHeader("Transfer-Encoding: "))) {
                    response.setBody(readChunkedBody());
                } else { 

At first I must say that there was an unrelated bug I inspected in VM but also found this one. If you run this minimal example on fastdebug vm (any vm will go, not just jdk8u232) you will get a crash like this. As far as I understand this has no impact on release VM and will never happen there. However I suppose this is important to fix to reduce amount of VM crashes you get when you debug it.

Hi! I built my app with one-nio 1.2.0 and it doesn't start. In logs I can see: /usr/bin/java: symbol lookup error: /tmp/libonenio.97307c0a.so: undefined symbol: OPENSSL_init_ssl Both servers: where I built and where I tryed to start, have openssl version 1.0.2k-fips What I should do?

Basically what I am missing from the library:

• Put ByteBuffer or native memory body into the http response
• Have a completion listener

Let me know if you would do anything differently and I'll change it. Don't want to maintain my own fork of this. Thank you for making this library public. It is a charm to work with it and easy to extend.

I refined the code some more.

The only breaking change is this:

• QueueItem#release takes Throwable to signal problems. No-arg release method removed. It would be to much confusion which gets called. I think it is nice to have this. But don't mind if we don't. I only care to know if written == totalCount meaning everything is sent.

At the moment the read method of for example LocalDate is generated to something like this

public final Object read(DataStream var1) throws IOException, ClassNotFoundException {
    LocalDate var2;
    var1.register(var2 = new LocalDate);
    JavaInternals.unsafe.putInt(var2, 12L, var1.readInt());
    JavaInternals.unsafe.putShort(var2, 16L, var1.readShort());
    JavaInternals.unsafe.putShort(var2, 18L, var1.readShort());
    var2.readObject(NullObjectInputStream.INSTANCE);
    return var2;
}

But the LocalDate#readObject will throw InvalidObjectException because it uses serialization proxy java.time.Ser. The simple solution is to exclude calling of this method from generated code like this:

Repository.setOptions(LocalDate.class, Repository.SKIP_READ_OBJECT);
// ... same for all java.time.* classes

However it could be made in a general way if we check for presence of writeReplace method and exclude readObject automatically. Do you have plans for this? I suppose I can make a PR, it looks like a simple condition in DelegateGenerator#generateRead.

При использовании библиотеки наткнулся на небольшую проблему. Нельзя было задать обьектам свои имена. Теперь проблему решил добавлением аннотации, теперь не нужно делать названия переменных в виде - "error_text" и т.п.

Привет!

Получаю ошибку при попытке десериализовать класс у которого есть поле типа ReentrantLock. Следующий код

DeserializeStream stream = new DeserializeStream( bytes );
return ( T )stream.readObject();

выбрасывает exception java.lang.IllegalAccessError: java/util/concurrent/locks/ReentrantLock$Sync

Hi! Please tell us more about BUFFER_SIZE=8000 meaning. What if response bigger than 8000 bytes? If I'm sure that almost all my responses have less than 6000 bytes, does it mean that I should set BUFFER_SIZE=6000?

Is there any tutorial 'hot to use serializer'?

I have serveral questions:

1. Did I right understand that a work do through

• one.nio.serial.Serializer#serialize
• one.nio.serial.Serializer#deserialize Is it the best (for perfomance) way?

2. What is the difference between persist and serialize?
3. You told that there is a feature to request a schema. I didn't find it =(
4. Can I add a custom Serializer for my type?

Thanks!

I find the Socket is missing join/leave multicast support. Any plans to add it? Why was this left out? Would it be fine if this gets included?

I made a quick try without native support here 65bc2aa8e577f9a06a195ebfa8cd867c1bbf744e. Would the API changed be acceptable?

• on linux unicode problems without + 10 (JsonReader#readHexChar)
• call no-arg constructor if annotated with @Before (needed for e.g. field init)
• if long value outside javascript safe integer range write it as String
• support reading long field as String
• support reading boolean filed as String
• support reading String field as boolean or number

Deserialization BigDecimal with Java 1.8.0_351 does not work any more:

java.io.IOException: readObject() is not fully supported. See implementation notes.
	at one.nio.serial.gen.NullObjectInputStream.unsupported(NullObjectInputStream.java:170)
	at one.nio.serial.gen.NullObjectInputStream.readFields(NullObjectInputStream.java:50)
	at java.math.BigDecimal.readObject(BigDecimal.java:3798)
	at sun.reflect.Delegate14_BigDecimal.read(Unknown Source)
	at one.nio.serial.GeneratedSerializer.read(GeneratedSerializer.java:127)
	at one.nio.serial.DeserializeStream.readObject(DeserializeStream.java:75)
...

Serialization BigInteger with different versions of Java produces different result

    byte[] res;
    try (PersistStream stream = new PersistStream()) {
      stream.writeObject(new BigInteger("123"));
      res = stream.toByteArray();
    }
    System.out.println(res.length + " bytes, hash=" + Arrays.hashCode(res));

Java 8 output: 141 bytes, hash=-1637736666 Java 11 and 17 output: 169 bytes, hash=1514769574

If BigInteger serialized with Java 8 and deserialized with Java 11

    try (DeserializeStream des = new DeserializeStream(res)) {
      System.out.println(des.readObject());
    }

Output:

Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Stream field is missed locally: int java.math.BigInteger.bitCount
Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Stream field is missed locally: int java.math.BigInteger.bitLength
Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Stream field is missed locally: int java.math.BigInteger.lowestSetBit
Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Stream field is missed locally: int java.math.BigInteger.firstNonzeroIntNum
Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Local field is missed in stream: int java.math.BigInteger.bitCountPlusOne
Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Local field is missed in stream: int java.math.BigInteger.bitLengthPlusOne
Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Local field is missed in stream: int java.math.BigInteger.lowestSetBitPlusTwo
Jul 15, 2022 4:14:09 PM one.nio.serial.Repository logFieldMismatch
WARNING: [1b5f8d93540f6312] Local field is missed in stream: int java.math.BigInteger.firstNonzeroIntNumPlusTwo
123

If vice versa Output:

Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Stream field is missed locally: int java.math.BigInteger.bitCountPlusOne
Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Stream field is missed locally: int java.math.BigInteger.bitLengthPlusOne
Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Stream field is missed locally: int java.math.BigInteger.lowestSetBitPlusTwo
Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Stream field is missed locally: int java.math.BigInteger.firstNonzeroIntNumPlusTwo
Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Local field is missed in stream: int java.math.BigInteger.bitCount
Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Local field is missed in stream: int java.math.BigInteger.bitLength
Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Local field is missed in stream: int java.math.BigInteger.lowestSetBit
Jul 15, 2022 4:14:59 PM one.nio.serial.Repository logFieldMismatch
WARNING: [4b1f962d58472cfa] Local field is missed in stream: int java.math.BigInteger.firstNonzeroIntNum
123

I want to add a user login check handler in my application when using the HttpServer, but I can't find a graceful way to do this in one.nio.http package.