Okay, so I branched Twisted to start the web rewrite in twisted.web now, since it has been declared that the tmlabs name change isn't going to happen. This leaves the web rewrite without a reasonable home, but for now, we're going to ignore that. So, web rewrite is just going to happen in a branched copy of twisted.web. This may not be its final home, because it is not a goal to be completely API compatible, but for now, that is where it's going to be hacked upon. Once the whole naming thing is *actually* decided, we can move it somewhere else.
svn://svn.twistedmatrix.com/svn/Twisted/branches/new-web
Somewhat repeating my earlier email: here's what's going to happen on this branch: - Rewrite of http.py - Removal of old cruft - Integration of Nevow generic web stuff: appserver, guard. - Fixup of rest of files to work right with nevow-originated API changes.
I will continue working on http.py separately in my sandbox until it mostly works, and will integrate with this branch then. dreid has said he'll start working on integration of nevow generic web stuff and removal of ancient cruft once he bludgeons radix into giving him commit access.
Open question: does Nevow go into twisted/web/? If so, how do we handle standalone (not depending on twisted at all) nevow? Perhaps standalone nevow is just a branch of twisted/web/nevow/ with appropriate modifications? If nevow isn't a package in twisted/web, dirlist and failure can't go into twisted.web because they depend on Nevow.
James
On Apr 24, 2004, at 3:34 AM, James Y Knight wrote:
Open question: does Nevow go into twisted/web/? If so, how do we handle standalone (not depending on twisted at all) nevow? Perhaps standalone nevow is just a branch of twisted/web/nevow/ with appropriate modifications? If nevow isn't a package in twisted/web, dirlist and failure can't go into twisted.web because they depend on Nevow.
Here is what I am thinking: Nevow should be a standalone package, but should also be included with twisted.web. I would prefer that nevow *not* be included in the twisted. package, but be shipped with the twisted.web tarball.
dp
On Sat, 2004-04-24 at 17:26, Donovan Preston wrote:
On Apr 24, 2004, at 3:34 AM, James Y Knight wrote:
Open question: does Nevow go into twisted/web/? If so, how do we handle standalone (not depending on twisted at all) nevow? Perhaps standalone nevow is just a branch of twisted/web/nevow/ with appropriate modifications? If nevow isn't a package in twisted/web, dirlist and failure can't go into twisted.web because they depend on Nevow.
Here is what I am thinking: Nevow should be a standalone package, but should also be included with twisted.web. I would prefer that nevow *not* be included in the twisted. package, but be shipped with the twisted.web tarball.
I agree that Nevow should be a standalone framework but I'm not convinced that bundling Nevow with t.web is good for either of them.
t.web (http protocol, request/resource interface, http client and http server (including vhost, ditrib, rewrite, etc)) makes a great base for web application frameworks, web services, web servers etc. Once the current limitations have been addressed I doubt there will be a great need for further releases other than bug fixing.
Nevow is an application framework. Its requirements are largely driven by applications, much more so than t.web anyway. I suspect that Nevow will need more frequest updates than t.web, i.e. even smarter form processing, pluggable validation and general refactoring to support more use cases. Many of these requirements will only become apparent as the application are developed.
So to summarise ... I think a stable http+t.web and an evolving, uber-cool Nevow, distributed separately, would be the ideal solution.
I do realise that there is some overlap between t.web and a useful, standalone Nevow (app server, static, not found etc) and I haven't got any great ideas about how to "solve" that issue.
Cheers, Matt
Matt Goodall matt@pollenation.net writes:
On Sat, 2004-04-24 at 17:26, Donovan Preston wrote:
On Apr 24, 2004, at 3:34 AM, James Y Knight wrote:
Open question: does Nevow go into twisted/web/? If so, how do we handle standalone (not depending on twisted at all) nevow? Perhaps standalone nevow is just a branch of twisted/web/nevow/ with appropriate modifications? If nevow isn't a package in twisted/web, dirlist and failure can't go into twisted.web because they depend on Nevow.
Here is what I am thinking: Nevow should be a standalone package, but should also be included with twisted.web. I would prefer that nevow *not* be included in the twisted. package, but be shipped with the twisted.web tarball.
I agree that Nevow should be a standalone framework but I'm not convinced that bundling Nevow with t.web is good for either of them.
t.web (http protocol, request/resource interface, http client and http server (including vhost, ditrib, rewrite, etc)) makes a great base for web application frameworks, web services, web servers etc. Once the current limitations have been addressed I doubt there will be a great need for further releases other than bug fixing.
Could we imagine that t.web become part of standard lib of python ?
On Sun, Apr 25, 2004 at 07:32:37PM +0200, William Dode wrote:
Could we imagine that t.web become part of standard lib of python ?
Only in nightmares.
Python standard lib stuff is *extremely* stable, we don't have the power to remake/break the api, etc, if its in the standard lib.
I believe the feeling is that we're better off being completely seperate from the python standard libraries, for that reason.
Stephen.
participants (5)
-
Donovan Preston -
James Y Knight -
Matt Goodall -
Stephen Thorne -
William Dode