I'm kicking off this discussion on the mailing list as I don't have
anything well-formed enough to take to the bug tracker, and I am hoping to
get some more engagement on the matter.
Currently there is no way to explicitly compose Twisted endpoints, but
several endpoint implementations have arisen
Tristan Seligmann writes:
> Currently there is no way to explicitly compose Twisted endpoints, but
> several endpoint implementations have arisen that explicitly wrap
> another endpoint, and so have needed a way to do this.
A couple other examples:
Autobahn provides 'Web Application Messaging P
> On Sep 6, 2016, at 11:55 AM, Tristan Seligmann
> wrote:
>
> Currently there is no way to explicitly compose Twisted endpoints, but
> several endpoint implementations have arisen that explicitly wrap another
> endpoint, and so have needed a way to do this. So far, this has been
> implementi
I'm not opposed to a fresh syntax, but I do believe the current
implementation can be used for composition. The parser for endpoint strings
is simplistic, like Glyph points out, but there is nothing preventing it
from having nested endpoint definitions. We used the existing syntax when
writing the
