I'd further note that ClientService is generally the new, good way to do things and ReconnectingClientFactory is the old, bad way. Our hope is to eventually deprecate ReconnectingClientFactory and most of the APIs that it uses, but this is a big project that we have not been able to make much progress on in the last, ahem, decade or so.
-g > On Mar 22, 2019, at 4:28 PM, Chris Satterthwaite <ch...@cmsconstruct.com> > wrote: > > Hi Sean, > > Thanks for the suggestion; I’ll take a look. > > -Chris > > > From: Twisted-Python <twisted-python-boun...@twistedmatrix.com> On Behalf Of > Sean DiZazzo > Sent: Friday, March 22, 2019 3:09 PM > To: Twisted general discussion <twisted-python@twistedmatrix.com> > Subject: Re: [Twisted-Python] stop/start client connections with > loseConnection in ReconnectingClientFactory > > You may want to look at twisted.application.internet.ClientService > <https://twistedmatrix.com/documents/18.7.0/api/twisted.application.internet.ClientService.html>. > It uses the new endpoints instead of the `connectTCP()` stuff. Not sure if > it applies in your situation, but it has all of the retry logic built in, so > that may make it easier to work with. > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
