Benoit Foucher

We could use a much smaller value such as 16. Or if it's still to large simply create a Slice decoder for decoding each element. We've optimized the Slice decoder...

Updated the title of the issue, the callback is actually not for verification purposes. It's about providing different connection options based on the server name/ssl protocols. See the motivation for...

Http cookies use Http request/response headers and are formatted as strings. `icerpc` cookies would use request/response fields and can just contain binary data. Cookies are well understood and used a...

Note that it's the cookie value which would be transferred as bytes. A cookie would typically be encoded as a Slice2 struct with additional attributes: ``` struct Cookie { value:...

Fixed the CI failures: - server idle time bug - FD limit bug I've also disabled the failing idle timeout test.

> Graceful closure with the ice protocol relies on the peer closing (aborting) the transport connection. Why abort? The protocol waits for the close connection message from the peer and...

> Note that this behavior currently depends on setting a synchronization context on the threads of the Ice client thread pool. Without this synchronization context, the continuation would execute in...

One potential issue with the per-communicator caching of classes is for application servers that might load/unload apps. How do we ensure that the classes for unloaded apps are cleared from...