Yakiv Yereskovskyi
07/23/2026, 6:10 PMKotlin: Multiple parameters are not allowed in @Grpc service functions.
Any plans to serialize multiple parameters as a single grpc message?Yakiv Yereskovskyi
07/23/2026, 6:46 PMAlexander Sysoev
07/23/2026, 6:49 PMYakiv Yereskovskyi
07/24/2026, 9:47 AMsuspend fun findAll(
filter: BuyerFilter,
pageParams: PageParams,
): PageResult<Buyer>Alexander Sysoev
07/24/2026, 9:51 AMAlexander Sysoev
07/24/2026, 9:51 AMYakiv Yereskovskyi
07/24/2026, 9:54 AMYakiv Yereskovskyi
07/24/2026, 9:54 AMAlexander Sysoev
07/24/2026, 9:54 AMwith no proto mode do not care about idiomatic usage of the protocolI wouldn't say this is the best approach to do things
Yakiv Yereskovskyi
07/24/2026, 9:56 AMAlexander Sysoev
07/24/2026, 9:57 AMit’s kinda one of the main usecases of the lib IMO, being able to use kotlin interfaces as a contract and currently it’s not supportedit is fair for kRPC, but not for gRPC. gRPC is for using gRPC in KMP, and playing by the gRPC rules. We can make it nicer where we can, but still respecting the gRPC conventions and rules kRPC, on the other hand, is to be Kotlin-first, yes, and I would love to see it shine too. But we have to prioritize things now, and kRPC is waiting for its turn for now
Yakiv Yereskovskyi
07/24/2026, 10:02 AMAlexander Sysoev
07/24/2026, 10:09 AMYakiv Yereskovskyi
07/24/2026, 10:12 AMgRPC is generally considered to be quite fast protocol, what overhead do you have?that’s what I’m saying, it’s faster and more robust than http protocol in kRPC, main overhead of your own protocol is service messages, especially given the fact I’m creating new connection on every request
Alexander Sysoev
07/24/2026, 10:16 AMYakiv Yereskovskyi
07/24/2026, 10:19 AM