Hi Godson - thanks for the reply... I had tried disowning the parent. I was actually getting unexpected behaviour on setServiceParent, but that's another story. I'll try again with TCPServer tomorrow, but for now I'm just keen to know if there are any bad interactions between Applications and listenTCP.
Thanks D On 12 May 2010 00:44, Godson Gera <[email protected]> wrote: > you can call 'disownServiceParent' when you don't want them to be in service > any more. That will cause it to stop listening. > > http://twistedmatrix.com/documents/10.0.0/api/twisted.application.service.Service.html#disownServiceParent > > > On Tue, May 11, 2010 at 5:47 PM, Donal McMullan <[email protected]> > wrote: >> >> I've got a server application that listens on a port, and when clients >> connect, spawns another TCP service on a random port that can live >> from a few seconds, up to a day or two. >> >> I had some problems getting this to work with >> twisted.application.internet.TCPServer (my services wouldn't stop >> listening when I'd finished with them) but it's working ok with plain >> old reactor.listenTCP. >> >> I don't really grok the TAC thing yet, or why there's a different >> method for spawning servers within an Application. Is my listenTCP >> approach bad practice for some reason that's not apparent to me? >> >> Thanks! >> >> Donal >> >> _______________________________________________ >> Twisted-Python mailing list >> [email protected] >> http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > > > > -- > Thanks & Regards, > Godson Gera > IVR India > > _______________________________________________ > Twisted-Python mailing list > [email protected] > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > > _______________________________________________ Twisted-Python mailing list [email protected] http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
