<br><br><div><span class="gmail_quote">On 4/15/06, <b class="gmail_sendername">Mike Pelletier</b> <<a href="mailto:mike@mkp.ca">mike@mkp.ca</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There has also been debate about whether or not mktap plugins are even a good<br>idea at all for new applications. At any rate, I don't think it receives the<br>same attention from the core developers that it once did. The moral seems to
<br>be that just because something is provided by Twisted does not mean it's a<br>best practice.</blockquote><div><br>Thanks for the reply.<br><br>So, if the docs tell us that this way is the way to use twisted, and they're wrong, where do we go to learn how to use twisted?
<br><br>The docs are quite clear about using application objects and making your code into a twisted 'plugin' rather than simply poking at the reactor (as in some of the quick-n-dirty tutorials).<br><br>I can certainly write my own persistence code, but I'm a little worried that more of the "best practices" presented by the docs are wrong. Should I still use twistd? Should I use the application object? Etc.
<br><br>Shorter (and somewhat snippier): how do we use twisted in our projects, if the docs are wrong?<br><br>I know that you personally aren't responsible to answer this question; I'm hoping some others might pipe in and point me to some other docs or other tutorials.
<br><br>Thanks.<br></div><br></div><br>