After offline discussions, a change has been made to the proposal. If a default service config was provided as a channel argument, then that config would be a valid service config to use if there was no valid resolved service config to use.
On Monday, September 17, 2018 at 5:57:42 PM UTC-7, [email protected] wrote: > > This is the discussion thread for the proposal at > https://github.com/grpc/proposal/pull/100. > > The proposal provides a way to treat errors in service configs. > > If a service config (JSON formatted) received is badly formatted or > contains invalid values for known fields, the client should ignore that > service config in its entirety. Unknown fields in the service config should > be ignored. If there was a service config that the client was previously > using, it shall continue using those parameters when communicating with the > service. If there was no service config being used, then the client shall > continue behaving as if it never received a service config update from the > resolver. On the other hand, if it is a new client, then the client should > fail to start, i.e., not act on the resolution result till a valid service > config is received. > > -- 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/531780a1-0061-45ad-863c-18e87d2b61cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
