Dominik Charousset

Wise or not, JSON actually *requires* encoding non-printable characters in this way (https://www.ietf.org/rfc/rfc4627.txt): > All Unicode characters may be placed within the quotation marks except for the characters that must...

Thanks for reporting! Doing the manual dispose shouldn't be necessary, but we'll have to dig into it to see why it makes a difference.

A graceful connection close should send a close frames. IIRC, we do that in the code. Could it be that we just don't give the socker manager an opportunity to...

@riemass what about the JOSN reader? Do we already support the `\xxxx` syntax there? I would like to see a roundtrip test. If that would require touching the parser and...

Using local encoding would go against the spec (see 8.1): > JSON text exchanged between systems that are not part of a closed ecosystem MUST be encoded using UTF-8 [[RFC3629](https://www.rfc-editor.org/rfc/rfc3629)]....

Thanks for filing the ticket! The current behavior definitely isn't intuitive. After thinking a bit more about it, I'd even lean towards classifying it as a bug instead.

This might be more complicated. The fixture calls `resume` on an actor, but there's no indication on whether an actor has actually consumed a message from its mailbox. Since this...

Welcome to CAF! Thanks for reporting. It certainly makes sense to extend the client API. On the server side, users can already access all HTTP fields, so it makes little...

This has landed in `main` and will be included in CAF 2.

Shouldn't `multipart` be transparent to CAF since it only affects how to parse the payload? That error looks like it's rejecting the first line of the HTTP header. Looking at...