> Do you have a suggestion or an example of how this might be used?
The idea I have in my head isn't backwards compatible, but I was thinking
of something like
haproxy:(tls:hostname.example:endpoint=(tcp:7.6.5.4:443))
This would break any endpoint description that starts with `(` but allows
arb
> On Oct 12, 2016, at 2:11 PM, Tom Prince wrote:
>
> I think if we are reconsidering the endpoint syntax, we should explicitly
> have nested delimiters for quoting (so something like () or {}), to easily
> allow multiple levels of nested endpoint strings (or any other kind of
> string).
Do y
I think if we are reconsidering the endpoint syntax, we should explicitly
have nested delimiters for quoting (so something like () or {}), to easily
allow multiple levels of nested endpoint strings (or any other kind of
string).
___
Twisted-Python mailing
On this note, if anyone wanted to write a greenfield gRPC implementation for
Twisted directly, rather than using the C++ library that Nathaniel has been
working on, hyper-h2 and Twisted’s built-in HTTP/2 logic is likely to be a very
useful leaping off point. My high-level understanding of gRPC i
