Thanks for the reply.<div><br></div><div>Very interesting thought. I had used the service for some work, but hadn't thought I should use it to put business logic in.</div><div><br></div><div>So thanks for the information.</div>
<div><br></div><div>John Aherne</div><div><br><br><div class="gmail_quote">On Fri, Jan 2, 2009 at 10:21 PM, Jarrod Roberson <span dir="ltr"><<a href="mailto:jarrod@vertigrated.com">jarrod@vertigrated.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br><br><div class="gmail_quote"><div class="Ih2E3d">On Fri, Jan 2, 2009 at 5:14 AM, John Aherne <span dir="ltr"><<a href="mailto:johnaherne@rocs.co.uk" target="_blank">johnaherne@rocs.co.uk</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">
One thing that has been puzzling me is where is the best place to put
application code.
</blockquote></div><div><br>business logic should go in the "Service" class.<br> <br></div></div><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>
<br></blockquote></div><br></div>