synchronous backend?

[c-cube]

some projects don't use lwt (lots of synchronous code). A blocking backend would be very useful.

[talex5]

The core capnp-rpc library doesn't depend on Lwt, but you'd still need to replace it with something else. Fundamentally, capnp-rpc is a promise library (like Lwt), but in which the promises can also be remote. For blocking programs, you'd probably be better off using plain capnp (without the RPC stuff).

[c-cube]

Fair enough, my use case is clients that don't need concurrency (open one connection and pretend calls are blocking).

[LasseBlaauwbroek]

I would also be interested in a blocking (non-lwt) backend.