you can call 'disownServiceParent' when you don't want them to be in service any more. That will cause it to stop listening.<br><br><a href="http://twistedmatrix.com/documents/10.0.0/api/twisted.application.service.Service.html#disownServiceParent">http://twistedmatrix.com/documents/10.0.0/api/twisted.application.service.Service.html#disownServiceParent</a><br>
<br><br><div class="gmail_quote">On Tue, May 11, 2010 at 5:47 PM, Donal McMullan <span dir="ltr"><<a href="mailto:donal.mcmullan@gmail.com">donal.mcmullan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I've got a server application that listens on a port, and when clients<br>
connect, spawns another TCP service on a random port that can live<br>
from a few seconds, up to a day or two.<br>
<br>
I had some problems getting this to work with<br>
twisted.application.internet.TCPServer (my services wouldn't stop<br>
listening when I'd finished with them) but it's working ok with plain<br>
old reactor.listenTCP.<br>
<br>
I don't really grok the TAC thing yet, or why there's a different<br>
method for spawning servers within an Application. Is my listenTCP<br>
approach bad practice for some reason that's not apparent to me?<br>
<br>
Thanks!<br>
<br>
Donal<br>
<br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Thanks & Regards,<br>Godson Gera<br><a href="http://godson.in">IVR India</a><br>