Unpack List<List<MessagePackObject>>( List of List) about msgpack-cli HOT 4 CLOSED

Hi.

No, it might be caused by an Unpacker bug or a corrupt data. Could you tell
me what bytes did you try?

Thank you!

from msgpack-cli.

Sorry, the byte array is too complex, my use case is:

1. Java Server read data from database, use msgpack-java to pack the list<list<Value>> to the network
2. C# Client read data from network, unpack it back to List<List<MessagePackObject>>

The exception only throws when the client read too fast, if I put the java server to sleep some time, the client will work as expected, could it be Unpacker bug of reading the wrong byte.

BTW, I'm doing it synchronously, so it can not be synchronized bug.

Thanks!

from msgpack-cli.

Oops! My post is pending in the browser over 10 days. Sorry for too late response.

Unpacker does not treat synchronization related matter, it relies on that underlying Stream returns proper bytes. So I guess it is synchronization issue of underlying data because server response speed caused failure, although you don't think so.

Please ensure that your networking layer correctly implement, for example:

1. Client ant server uses dedicated connection per session.
2. Server synchronize writing its response to the buffer per session.
3. Client synchronize reading from the response buffer per session.

Thanks!

from msgpack-cli.

Close because this Q&A is staled.

from msgpack-cli.