[Twisted-Python] .tap and twistd and persistence

[Christopher Armstrong]

On 4/17/06, Matt Feifarek <matt.feifarek+twisted at gmail.com> wrote:
>
>
>
> On 4/15/06, Mike Pelletier <mike at mkp.ca> wrote:
> >
> > There has also been debate about whether or not mktap plugins are even a
> > good
> > idea at all for new applications.  At any rate, I don't think it
> > receives the
> > same attention from the core developers that it once did.  The moral
> > seems to
> > be that just because something is provided by Twisted does not mean it's
> > a
> > best practice.
>
>
> Thanks for the reply.
>
> 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?
>
> 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).
>
> 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.
>
> Shorter (and somewhat snippier): how do we use twisted in our projects, if
> the docs are wrong?
>
> 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.
>



Please point us at the docs that are wrong (hopefully in the bug tracker),
and give them the "documentation" keyword.




--
Christopher Armstrong
International Man of Twistery
http://radix.twistedmatrix.com/
http://twistedmatrix.com/
http://canonical.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/twisted-python/attachments/20060417/6242d36a/attachment.html>