Re: [Twisted-Python] sharing a dict between child processes

If you need guaranteed delivery of the data, why not just use a TCP connection to the unix socket, instead of a UDP connection which inherently can lose data? In that case I don't think your patch would be needed. I didn't look at the source, so perhaps I missed something. On Wed, Nov 6, 2019

Re: [Twisted-Python] PyOpenSSL empty socket property

Perhaps this line from OpenSSL.SSL.Connection is a clue. "socket may be None; in this case, the Connection is created with a memory BIO: see the bio_read(), bio_write(), and bio_shutdown() methods." https://www.pyopenssl.org/en/stable/api/ssl.html#OpenSSL.SSL.Connection On Wed, Sep 4, 2019 at

Re: [Twisted-Python] Twisted tips for designing highly concurrent twisted REST API

Klein and Crossbar.io seem relevant as well https://crossbario.com/blog/Going-Asynchronous-from-Flask-to-Twisted-Klein/ On Thu, Jul 11, 2019 at 1:46 AM Scott, Barry wrote: > On Tuesday, 9 July 2019 22:04:11 BST Tom Most wrote: > > ...snip... > > > The reactor's own thread pool is really for

Re: [Twisted-Python] how to get extReceived call from SSHCommandClientEndpoint

It looks like extReceived() is a method of SSHSession.Channel.SSHChannel . You can access it through the protocol's transport. self.transport.conn.channels[0].extReceived() ~Sean On Fri, Apr 5,

Re: [Twisted-Python] Can transport.write() to hostname instead of IP address?

wrote: > On Aug 17, 2018, at 9:24 AM, Sean DiZazzo wrote: > > > Starting to look over the docs and I realize I might have just been able > to incorporate the `optionsForClientTLS` into what I was already using. > > I was using `reactor.connectSSL()` with a default > ``ssl.Client

Re: [Twisted-Python] Can transport.write() to hostname instead of IP address?

to the endpoint examples. Thanks again! On Thu, Aug 16, 2018 at 9:06 PM, Sean DiZazzo wrote: > To summarize, you are writing a client application using Twisted which >> needs to talk with a service behind an Nginx reverse proxy. The reverse >> proxy requires use of TLS (a.k.a. SSL) and

Re: [Twisted-Python] Can transport.write() to hostname instead of IP address?

fire with a protocol instance generated > by the factory passed to connect(). > > This is basically what Agent does internally, as I understand it. > > Hope this helps, > Tom > > On Thu, Aug 16, 2018, at 6:44 PM, Sean DiZazzo wrote: > > I guess thats still kind of co

Re: [Twisted-Python] Can transport.write() to hostname instead of IP address?

ds packets to myprotocol.example.com:443 instead of 23.23.23.23:443. Nginx reference: http://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html On Thu, Aug 16, 2018 at 6:14 PM, Sean DiZazzo wrote: > Thanks for responding, Adi! > > I don't want each packet to go it's own way from Twisted. They all go

Re: [Twisted-Python] Can transport.write() to hostname instead of IP address?

the packet correctly. On Thu, Aug 16, 2018 at 5:49 PM, Adi Roiban wrote: > On Fri, 17 Aug 2018 at 01:25, Sean DiZazzo wrote: > > > > Hi all! > > > > After I start a reactor connecting to a specific hostname and port, I do > my thing and then call transport.write(

[Twisted-Python] Can transport.write() to hostname instead of IP address?

Hi all! After I start a reactor connecting to a specific hostname and port, I do my thing and then call transport.write() to send the data to the peer. >From what I can tell, though, the hostname is resolved, and the data is written back to the ip address itself, instead of the hostname I