Right... we don't have an ack on the settings negotiation (which keeps
things simple) but there's otherwise no way to disambiguate base64 - and
the NUL has the nice property of being otherwise disallowed by http2.
On Fri, Apr 7, 2017 at 3:49 PM Louis Ryan wrote:
> Can you elaborate in the spec o
Can you elaborate in the spec on why the NUL prefix is needed? You mention
the alternatives but not why this is being done, I presume it's to
disambiguate with base64 encoded stuff while setting negotiation is in
flight.
Otherwise LGTM
+cc Piotr re our recent discussion about the IETF proposal fo
Very cool.
*Josh Humphries*
jh...@bluegosling.com
On Wed, Mar 29, 2017 at 1:28 PM, 'Eric Anderson' via grpc.io <
grpc-io@googlegroups.com> wrote:
> On Wed, Mar 29, 2017 at 10:10 AM, 'Craig Tiller' via grpc.io <
> grpc-io@googlegroups.com> wrote:
>
>> I've created a gRFC here https://github.
On Wed, Mar 29, 2017 at 10:10 AM, 'Craig Tiller' via grpc.io <
grpc-io@googlegroups.com> wrote:
> I've created a gRFC here https://github.com/grpc/proposal/pull/19 for a
> protocol change to allow -bin metadata elements to be transmitted in binary
> form.
>
The proposal LGTM. I made some comments
I've created a gRFC here https://github.com/grpc/proposal/pull/19 for a
protocol change to allow -bin metadata elements to be transmitted in binary
form.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receivin
