Skip to content

lifts 4mb restriction of gRPC messages#22

Open
chorin1 wants to merge 1 commit intogoogle:masterfrom
chorin1:unlimit-grpc-msg-size
Open

lifts 4mb restriction of gRPC messages#22
chorin1 wants to merge 1 commit intogoogle:masterfrom
chorin1:unlimit-grpc-msg-size

Conversation

@chorin1
Copy link

@chorin1 chorin1 commented Dec 13, 2020

Fixes issue #16.
This is ok for a POC, in real life scenario max message size should obviously be limited.

RasoulAM added a commit to RasoulAM/private-join-and-compute that referenced this pull request Aug 1, 2022
@Chuang1024
Copy link

Could you tell me the version of bazel that you use?I try to build this but I fail.

@karnseth karnseth closed this Oct 15, 2025
@karnseth karnseth reopened this Oct 15, 2025
FLAGS_paillier_modulus_size);

grpc::ChannelArguments ch_args;
ch_args.SetMaxReceiveMessageSize(-1); // consider limiting max message size
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Client uses -1 (unlimited), server uses INT_MAX. That’s probably intentional, and using -1 on ServerBuilder historically hasn’t always behaved as people expect, so INT_MAX is defensible.

Still, I’d prefer:

  • define a single constant / flag value used in both places, and
  • add a short comment explaining why server uses INT_MAX rather than -1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants