> > >
> > > It does? Then you need to find a clue. quick_handler should have been
> > > axed from the outset, and now that this handler allows a non-filesystem
> > > request to be handled properly, it really should be gone.
> >
> > map_to_storage is definitely not the same as quick_handler. But
> > quick_handler does have a use so it stays in.
>
> Actually, they are closer than you might think. quick_handler's purpose is to allow
> requests to be served as quickly as possible. It skips a lot of phases of the
> request to accomplish that. If map_to_storage is tweaked a bit, it can accomplish
> the same thing.
>
> Basically, the map_to_storage function that succeeds would tell the server how many
> of the hooks that follow map_to_storage that it should skip before the handler phase.
>
> This has a couple of advantages over quick_handler, the first one being that it
> is more general, and the second that it means we go back to having one location that
> data is sent to the network.
>
> If that change is made to map_to_storage, then I would be with OtherBill, and
> suggest that quick_handler should be removed.
>
Give me a while to experiment with getting mod_cache working with map_to_storage. I've
been considering moving quick_handler to after the first Location walk, which brings
the
functionality I am looking for very close to map_to_storage. We are meeting in the
middle
:-)
Bill
