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 grpc-io+u...@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/412dccb6-836e-4486-ab19-34701bec0562%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/3df76fa6-dd68-45cc-9548-c91b357d9d74%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAJhP0xBGECXFCB-Cui3r-ZKivj%3D4eUu1bv9qRRgBzO7G6jGy-A%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/954a4480-dc8f-42c6-ab68-44d884634e37%40googlegroups.com.
Which requires to run the server as a naked php process, which is still not a scalable, nor recommended solution by the php community itself, and is almost never supported by php web hosting services.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/c73bca19-479e-47ae-8166-e2a78f389a55%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CA%2BK14zE9xuUnkT_HW_MfaVBJW39zeZ31aZieY%3DXHDtRv5c4Eug%40mail.gmail.com.
The other languages (Ruby, Node.js, Python, C#, ...) don't have that issue, because they all have frameworks that are working properly from the command line. Right now, in order to run a gRPC python server, you can properly start a python daemon with your code in there. Node has everything built in for running servers without any front end. Ruby has been doing this natively as well for a long time.Unless somebody shows us otherwise, only PHP doesn't have any proper support to run a naked daemon. All the options that we've seen or that people have shown to us are toys or prototypes that aren't suitable for production usage. Basically, I'm challenging your "it is increasingly common to write standalone and daemonized PHP processes" and ask for proper examples and documentation that aren't flagged with warning labels such as "DO NOT USE FOR PRODUCTION".
You received this message because you are subscribed to a topic in the Google Groups "grpc.io" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/grpc-io/F3IyYaI_6S0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAHbcPLkhaccac9p%2BFXFkMG5r%2B0ed1JHDhGUHA%2BN3xRns8femoQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/0c67e504-d046-45d4-ae75-74cba27e5df6%40googlegroups.com.
Just a quick update -- we've cleared the open sourcing with the rest of the team and are working to extract some proprietary bits.Will get something up ASAP to be evaluated for admission into the gRPC ecosystem.
I would be very interested in trying this out.
There are several problems with the idea of a gRPC server in PHP, and we have no plans for that.Basically, the only way it would work, is if you run PHP "naked", without its typical nginx or apache frontend. You can't serve a long-lived streaming RPC from a PHP page using typical settings. The page will timeout very quickly. You could theoretically restrict yourselves to server unary RPCs only, or have an arbitrary duration on "streaming" RPCs, but that wouldn't be "gRPC" anymore. And even then, there's no proper HTTP/2 support in PHP at the moment. With the typical model of having a frontend that'll forward the requests to PHP processes spawned on the fly, you wouldn't have access to the full HTTP/2 stream, which is required to properly server gRPC requests.For more on that, I invite you to research how to serve websockets from PHP. Probably all of the solutions you'll find will be by running a naked PHP process, without Apache. That isn't the typical way people want to use PHP. So a gRPC server in PHP would be fairly useless as it'd require you to run it in a very atypical deployment environment.
Hey all—It appears as of right now you can only create CLIENTS in PHP, but not servers. I was wondering what the technical blockers behind this were and if it's on the roadmap for a future release?Thanks!