On Thu, Apr 14, 2005 at 07:05:03PM -0700, mso@oz.net wrote:
>   - Should parts of Quixote should be dropped in favor of
> WSGIKit-compatibility routines?

I may argue for a radical approach.  The aim of WSGI is to simplify
things, but we can't simplify if we're trying to stay compatible with
the messy past.

  * Keep PTL and htmltext.  They're useful, readable, and provide a security
benefit.
    WSGIkit would just have to be sure to call str() on what it receives
    to convert htmltext into a string.  A more radical course might use Unicode
    for everything, converting into an encoding for output.

    In essence, PTL is just another templating library.

  * Exception handling -- Quixote's is good and it separates out well.

  * Session handling -- Quixote's is OK, but not remarkable to my mind.
    The code needs some rearrangement to work in a WSGI world, basically to
break
    its dependency on the publisher currently in use.

  * Publishing -- can be simplified and reduced down to just the publishing
logic.
    I'm handicapped here by not really understanding the current
    Directory/namespace usage, because I've never updateddd an app for Quixote
2.0.

  * SCGI -- need to add an SCGI server option to Ian Bicking's WSGIkit.

Of course, this level of changes ends up looking like a completely new
set of components, not Quixote any more.

--amk