Thank you for the idea. I have not thought about oneof.
btw., I just started evaluating finalmq. It supports plain TCP, HTTP and
also mqtt together with protobuf and json. A browser can directly connect
to the application and can call the services. Also the communication via a
mqtt broker is possible.
A server can send events or requests to clients without needing an open
request from the client (at least the timer example looks very easy to me).
I was suprised, that it is even possible to call a service with plain
TCP/telnet like this:
/<servicename>/<messagename>!<correlationID>{jsondata}
Today, I will evaluate the performance.
[email protected] schrieb am Mittwoch, 27. Oktober 2021 um 19:18:39 UTC+2:
> > In case you decide for streaming interface.
> > As far as I know, for a streaming interface, you define one message
> type, which you can then send multiple times. But it is not possible to
> send different kind of messages to the peer over one streaming interface.
> > If you want to send only one type of message, then the streaming
> interface is good enough.
>
> This is not true. Suppose you want to send either FooMsg or BarMsg as a
> request msg, then just do this:
>
> message RequestMsg {
> oneof {
> FooMsg foo = 1;
> BarMsg bar = 2;
> }
> }
>
> On Tuesday, October 26, 2021 at 11:57:01 PM UTC-7 Eberhard Ludwig wrote:
>
>> In case you decide for streaming interface.
>> As far as I know, for a streaming interface, you define one message type,
>> which you can then send multiple times. But it is not possible to send
>> different kind of messages to the peer over one streaming interface.
>> If you want to send only one type of message, then the streaming
>> interface is good enough.
>>
>> If you plan to have a real bi-directional message exchange, then it is
>> worth to look for another technology.
>> I tried finalmq <https://github.com/bexoft/finalmq>, this looks quite
>> promising.
>>
>> Cheers
>> Eberhard
>>
>> Fabiano Ferronato schrieb am Montag, 18. Oktober 2021 um 18:09:45 UTC+2:
>>
>>> I have a problem to solve: one computer (PC) will send requests to many
>>> devices (e.g. RPi). The devices will execute the request and respond.
>>>
>>> Is it possible to use gRPC ?
>>>
>>> From the documentation (Introduction) it shows the opposite: clients
>>> sending requests to a server. So maybe I'm going the wrong way choosing
>>> gRPC.
>>>
>>> Any help is much appreciated.
>>>
>>>
>>>
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/grpc-io/f76e6df5-0174-4c89-80c6-fbd3d7143912n%40googlegroups.com.
