On Thu, Mar 2, 2017 at 9:24 AM, Mark D. Roth <[email protected]> wrote:
> On Thu, Mar 2, 2017 at 9:13 AM, Eric Gribkoff <[email protected]> > wrote: > >> On Thu, Mar 2, 2017 at 9:03 AM, 'Eric Anderson' via grpc.io < >> [email protected]> wrote: >> >>> The language is still confusing: >>> >>>> The client receives a non-error response from the server. Because of >>>> the gRPC wire specification, this will always be a Response-Headers frame >>>> containing the initial metadata. >>> >>> >>> What does "non-error response" mean there? I would have expected that >>> means receiving a Status in some way (which is part of Response), as >>> otherwise how is "error" decided. But the next part shows that isn't the >>> case since Status isn't in Response-Headers. >>> >>> >> The second sentence is defining what non-error response means: a >> Response-Headers frame. The only alternative (an "error" response) is >> Trailers-Only. I can chose a name other than "non-error response" to make >> this clear. >> > > It would probably be simpler to simply say "The RPC is committed when the > client receives Response-Headers." > It is possible to receive Trailers-Only in the non-error case, assuming streaming is supported. -- 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/CA%2B4M1oPv5z-fpsPJFaywkkE3SZYoKv%2BdiW14y8DedBV7UoUetQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
