Hi guys. De-lurking. Can't remember when I started lurking...
something about WSGI before. Anyway, back to harping on my typical topics.
Which is -- why aren't you guys embracing WSGI more? Here there's talk
of Unix compatibility, and SCGI servers and whatnot, and there's already
an SCGI threaded server if you really want it (in flup). Among several
other servers. I have to remind myself what Titus is doing too... you
have your own repository for a SCGI/WSGI server based on Quixote, right?
Anyway, seems like a natural direction for people who like simpler
things and less code, which seems to describe Quixote developers.
At the same time there's various packaging issues. People confuse
Quixote with PTL, even though they are only vaguely related. They
should be packaged separately. QP uses a module for configuration?
Yikes, makes me think of the accursed cherrypy.root (well, at least I
curse it).
Also, CherryPy and now RhubarbTart implement something very much like
Quixote. I know in RhubarbTart there are plans for pluggable
resolution, and exactly-like Quixote resolution would be possible and
useful (well, useful if someone actually wanted to move their app over
-- in practice I haven't seen many people make these kinds of
transitions, I'm not sure why -- maybe people are just more comfortable
converting a program wholesale).
So... I don't have any particular point. But I get this sense that no
one really feels like pushing Quixote onto a wider audience, and yet you
would like to participate in the larger goings-on, and it seems like
there's a way to do that. RhubarbTart, for instance, has a small scope
and a limited appeal, but if it can serve as a basis for more aggressive
frameworks (like TurboGears) then people who work at the lower level can
still benefit from the energy at that higher level.
--
Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
_______________________________________________
Quixote-users mailing list
[email protected]
http://mail.mems-exchange.org/mailman/listinfo/quixote-users
