Gregor Fabritius

It's quite common (and AFAIK good practice) to have a pointer type as parameter (not a reference) when you know this parameter's content may be changed by the function. If...

Okay, I've checked. The C interface needs a `zmq_msg_t*`, which conflicts if `send (message_t &msg_, int flags_ = 0)` becomes `send (const message_t &msg_, int flags_ = 0)` However, this...

Digging deeper: No need for (another) cost_cast. `message_t`'s `data()` has that already. So I propose `send()` becomes this: ``` inline bool send(const message_t& msg_, int flags_ = 0) { int...

Yeah, it is. I assumed that sending a message does _not_ modify it, but I am wrong. From the guide: > The zmq_msg_t structure passed to zmq_msg_send() is nullified during...

Any updates on this? I can start the plugin with Clion 2017.2 (not 2017.3, see #175), but include paths are not recognized and therefore navigation through code is impossible. Instead...

I think what @NikolaiBirolini meant was a c++ implementation of a grpc-web client. I'm looking for that as well. I have a c++ program that is built as wasm using...

Thanks for the update! for now I am just using http put/get and that's enough at the moment.

We tried different timeouts and approaches and were able to reduce network failure rate a bit, but we never achieved a stable UDP communication over multiple days due to the...

When switching to TCP we kept the asynchronous protocol we designed for UDP and are still experiencing problems. The protocol roughly works like this: - PC establishes TCP socket to...

> We'll switch to a request-based communication protocol and test again. Then there's nothing happening simultaneously and we can evaluate if this improves communication stability. We did that and tests...