On Mon, Jul 25, 2011 at 1:22 AM, Glyph Lefkowitz <glyph@twistedmatrix.com>wrote:
The main thing that web2 did wrong was introducing a new namespace and thereby confusion, not any particular detail of its implementation.
Well, my thing would introduce some namespaces (like "entity")-- just not one in the toplevel twisted package.
The web2 resource model was in most ways a nice upgrade from twisted.web. It even had a halfway decent compatibility layer. You should feel free to copy its implementation liberally (with the exception of the IStream interface, which has been discussed to death elsewhere). However, since web2 was half-baked in some regards, you may need to add test coverage, improve docstrings, or handle some corner cases in order to pass review.
Of course -- I'd end up doing that anyway because I wouldn't feel confident I understand the code otherwise.
But, in terms of implementation details, web2 was in fact "doing it right" for the most part.
Glad to know it's not just my mangled mind.
-glyph
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- cheers lvh