Hello folks,
I'm working on a project where we are planning to create a Google Assistant 
service instance on embedded/deeply embedded devices( non-linux, ARM 
processors running RTOS like ThreadX, FreeRTOS etc. )
Our system has support for building executables for c/c++ etc. but it is 
not same as linux( for example - no posix availability ).
Of course, like RTOSes these days, we have wrappers for providing 
OS/Networking functionality for applications/libraries to use.

My questions are:

i.   How fit gRPC is for embedded devices? I can see abstraction for 
different platforms in "port_platform.h" file used to build grpc-core with 
options given in the file.
     My first thought is it should be doable if I adapt port_platform.h and 
build grpc-core with the capabilities provided by our system.

ii.  How deep gRPC's love is for posix? If any platform/devices does not 
provide any posix-like high level APIs, will gRPC still work as expected? 
How straight-forward such a task is going to be?

iii. Any effort in community in bringing gRPC for embedded devices(for 
RTOSes) ? Would not it be great to have a tiny(and limited) gRPC library 
which can be
    easily integrated to embedded devices ? And such a thing supported by 
gRPC community/authors ?

I understand that I can get most of the answers from reading the code 
itself(which I'm doing btw).
But it would be nice to know insights/perspective of gRPC authors and 
community folks who understands gRPC better than me.

Open for suggestions/feedback.

Best regards,
Dharam

-- 
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/2248790d-feae-4d3c-930a-a325de68820a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to