An update with a general overview architecture, just for the one its 
interested in this approach:

<https://lh3.googleusercontent.com/-TLQYkIu9jIA/WfLadLJ5zUI/AAAAAAAAYg8/7Eqlra7TvK8goskDFQBcww9LnXCiyJ8ywCLcBGAs/s1600/IMG_8027.jpg>


On Thursday, October 26, 2017 at 3:20:42 PM UTC+2, [email protected] wrote:
>
> Hi all,
>
> Today I made a Go based prototype and proved that it's feasible. Next week 
> will have a free slot and will try to do it using c++ based library.
>
> Please take a look and give some feedback about the idea and the overall 
> architecture. As it was a prototype there is no even something similar to 
> code quality...hehe[1]
>
> Thanks,
>
> [1] https://github.com/glerchundi/grpc-boomerang
>
> On Wednesday, September 20, 2017 at 12:18:33 AM UTC+2, [email protected] 
> wrote:
>>
>> How interesting, I also need this for a project.  Both on client and 
>> server ends, I need to be able to provide my own FD (which was created by 
>> socketpair(), and inherited from a parent process via fork/exec).
>>
>> And for golang -and- Node.JS (Javascript).
>>
>> I was able to do this with Thrift with no trouble at all .... in C++, 
>> Ocaml, and golang so far.
>>
>> Is this possible?
>>
>> I notice that https://github.com/grpc/grpc/pull/6610 doesn't appear to 
>> cover golang, but only C++.
>>
>> On Monday, September 11, 2017 at 1:42:48 AM UTC-7, [email protected] 
>> wrote:
>>>
>>> Hello everyone,
>>>
>>> We are starting to design a new architecture based on a gRPC-first 
>>> approach. Every integration point we though of are well covered by the 
>>> actual gRPC design model except one. Our own hardware is deployed into our 
>>> clients infrastructure (a.k.a intranet) and I would like to:
>>> * Avoid intranet networking issues by letting devices connect to our 
>>> cloud as clients by using WebSockets.
>>> * Then interchange the roles by making our devices behave as gRPC Server 
>>> and the cloud as gRPC Client.
>>>
>>> We are thinking on deploying Go based backends and C and ARM based 
>>> embedded devices, which means *C-based WebSocket + gRPC Server* and 
>>> *Go-based 
>>> gRPC Client over WebSocket*, Is this architecture possible?
>>>
>>> I found some issues that may be related to this one but I'm not quite 
>>> sure. I'll point them anyways.
>>>
>>> Anyone which could shed some light on this topic would be really helpful!
>>>
>>> References:
>>> * Add support for communication using existing FD (for client and 
>>> server): https://github.com/grpc/grpc/pull/6610
>>> * assumes host:port style addresses, cannot easily use custom 
>>> transports, e.g. unix domain sockets: 
>>> https://github.com/grpc/grpc-go/issues/72
>>> * Support Unix domain socket: https://github.com/grpc/grpc-go/issues/73
>>> * support unix domain socket: https://github.com/grpc/grpc-go/pull/169
>>>
>>>
>>>

-- 
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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/grpc-io/1357e446-ec7c-4916-b6ab-2b87f4313499%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to