News for hackers. Stuff that matters.
Re:Why We’re Switching to gRPC by anderspitman on Saturday June 01, 2019 @03:30PM (#20071055)
Interesting. I do tend to favor protocols that are a bit lower level and more flexible for composing higher-level functionality. Though this does sound pretty complicated to implement using only what capnproto offers right now. Would there be a way to jury rig "request(n)" backpressure as described in reactive streams[0] (also implemented by RSocket[1]) on top of capnproto? That's what I'm using for omnistreams and it's proven very simple to reason implement and reason about.

[0] https://github.com/reactive-streams/reactive-streams-jvm

[1] http://rsocket.io/

[2] https://github.com/omnistreams/omnistreams-spec

Re:Why We’re Switching to gRPC by anderspitman on Saturday June 01, 2019 @03:31PM (#20071059)
Actually the more I think about it I don't think it would work, since request(n) assumes the producer can send multiple messages for each request.