[Twisted-Python] Patch: Passive getSession for twisted.web.server.Request

Glyph Lefkowitz glyph at twistedmatrix.com
Fri May 16 14:21:07 EDT 2003

On Friday, May 16, 2003, at 12:50 PM, Tom 'Korpios' Tobin wrote:

> Hmm.  I specifically don't like the way Woven works.

Woven is the Twisted web browser-based application framework.  The 
presence of browser-interaction features like sessions and cookies in 
twisted.web was really an accident due to the author's lack of 
appreciation for how these sorts of things worked at the time that he 
was writing it originally.  (ahem.)

If you don't like the templating system, don't use it :-), but that is 
only one part of what woven gives you.

> My preferred web development method is akin to Quixote; I really can't 
> stand HTML templating in the vein of PHP, etc.

To put Radix's comments more succinctly: dude, are you mental?  I think 
it would be difficult for Woven to have less in common with PHP and 
still talk to a web browser.  To the extent that it is analogous to 
previous work, it is most like Barracuda[1] or ZPT[2].

> That said, am I going to need to reimplement Session code down the 
> road due to this phase-out?

Probably at some point, but we tend to be very relaxed about web 
deprecations (even ones that TOTALLY suck, like twisted.web.widgets).  
The Session code in twisted.web.server is pretty fragile though, 
especially compared to the woven.guard stuff.

> Even if SessionWrapper works standalone without using the bulk of 
> Woven, I would much rather not be importing any Woven libraries 
> unnecessarily.

Don't worry about it.  In future releases of Twisted, woven will be 
imported for pretty much all the HTML generation that the web server 
will do internally, including directory listings and status pages.  
It's not all that much code.

	[1]: http://www.barracudamvc.org/
	[2]: http://www.zope.org/Documentation/Books/ZopeBook/current/ZPT.stx

More information about the Twisted-Python mailing list