Re: [Twisted-Python] gRPC support in Twisted Python

2016-10-12 Thread Cory Benfield 
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 is that at a 
wire-protocol level the other things required are some protocol buffers and 
some code generation. That’s definitely not *nothing*, but neither is it the 
same as implementing the whole thing in one go.

Cory


> On 7 Oct 2016, at 00:22, Nathaniel Manista  wrote:
> 
> On Thu, Oct 6, 2016 at 12:11 PM, Manish Tomar  > wrote:
> It will be nice if it can be implemented without IO [1] as Cory
> rightfully points out everywhere.
> 
> I'm a big fan of sans I/O; I think it will be interesting to see how much it 
> can be applied to the C-language library that implements most of the behavior 
> of gRPC Python.
> -N
> ___
> Twisted-Python mailing list
> Twisted-Python@twistedmatrix.com
> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Endpoint composition syntax

2016-10-12 Thread Tom Prince 
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 list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Endpoint composition syntax

2016-10-12 Thread Glyph Lefkowitz 

> 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 you have a suggestion or an example of how this might be used?

-g___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python

Re: [Twisted-Python] Endpoint composition syntax

2016-10-12 Thread Tom Prince 
> 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
arbitrarily nested endpoints (or even just date containing `:`).

Thinking about it some more, there isn't currently any endpoint
descriptions that have an empty name, so we could have a entirely new
syntax that starts with `:`. If we went in that direction, we'd definitely
want to think about future extensibility when designing it.
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python