Neil Schemenauer wrote:

>On Tue, Nov 23, 2004 at 08:45:47PM +0300, Oleg Broytmann wrote:
>
>
>>>    The _q_access hook is gone.
>>>
>>>
>>   How does one supposed to test authentication/authorization?
>>
>>
>
>Any way you want to, including using _q_access(). ;-)
>
>I thought I had deleted it but the 2.0a2 release still includes a
>mix-in class called AccessControlled.  E.g.
>
>    class MyDirectory(AccessControlled, Directory):
>
>        def _q_access(self):
>            ...
>
>If you like to have the request object as an argument, you can write
>your own mixin.  We have decided to use utility functions for access
>control. E.g.
>
>    class MyDirectory(Directory):
>
>        def _q_index(self):
>            check_access()
>            ...
>
>

Neil, it's clear that a great deal of work has gone into Quixote 2.0,
and you all deserve congratulations for that. It's also clear that
Quixote 2.0 represents a significant change in thinking in many
respects: more global accessors, fewer passed parameters,
object-oriented constructions such as Directory, Access-control mixins, etc.

I'm glad to see the progress that you have made, and that there's life
in Quixote. But I'm also extremely delighted with Quixote 1, and will
probably not be joining in on the Qx2 party unless some burning need
arises. That being said, I'm just whether there is a plan to maintain either

    * a 1.x compatibility layer, or
    * a 1.x bugfix branch

I can maintain my own 1.x branch if needed, of course. But there must be
others who have "legacy" or "heritage" Quixote applications, for whom
Quixote 1.x cannot simply go away, yet for whom a rewrite would be a
costly undertaking.

Best wishes,

-- Graham