* multi bvar support. This feature has been used and verified by many
business lines inside Baidu
Related PR:
https://github.com/apache/incubator-brpc/pull/1608

Warm Regards,
serverglen


Shuai Liu <[email protected]> 于2022年4月23日周六 22:23写道:

> * GRPC Stream support. Stream is a common feature of RPC
> frameworks, Although bRPC has Streaming RPC interface, bRPC will definitely
> be used in more scenarios if GRPC Stream is supported.
> Related issue:
> https://github.com/apache/incubator-brpc/issues/1589
> https://github.com/apache/incubator-brpc/issues/642
> https://github.com/apache/incubator-brpc/issues/680
>
> Warm Regards,
> serverglen
>
>
> 谭中意 <[email protected]> 于2022年4月19日周二 11:39写道:
>
>> I like these two features。
>>
>> On Mon, Apr 18, 2022 at 5:56 PM Weibing Wang <[email protected]> wrote:
>>
>> > Hello bRPC developers,
>> >
>> > Since bRPC 1.1.0 has been released:
>> > https://github.com/apache/incubator-brpc/releases/tag/1.1.0
>> > I would like to discuss with you what to include in the next release
>> > (1.2.0).
>> >
>> > You can reply to this email with a list of features or bug fixes you
>> > would like to include in the next release. You'd better give a reason
>> > why it's important for the next release.
>> >
>> > Let me start first, I think the following features are important for
>> > the next release:
>> > * arm64 support. We are encountering more and more arm scenarios, and
>> > running server-side applications on arm64 is a trend. Related issue:
>> > https://github.com/apache/incubator-brpc/issues/1407
>> > * New version gcc support. Currently master fails to compile in gcc
>> > 11.2.0 and 12.0.1, I think we need to fix it. Related issue:
>> > https://github.com/apache/incubator-brpc/issues/1693`
>> <https://github.com/apache/incubator-brpc/issues/1693>
>> > <https://github.com/apache/incubator-brpc/issues/1693>
>> >
>> > Looking forward to your reply!
>> >
>> > Thanks
>> > Weibing Wang
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>> >
>>
>

Reply via email to