-> > The critical issue is the authentication cookie (I'm assuming that's
-> > how Gallery works...).  If you can write a Python system that sets
-> > that cookie in a fashion that Gallery will accept, then the rest
-> > should "just work".
-> >
-> > If you can make the Quixote system accept the Gallery auth cookie,
-> > then you could use either, or both, systems for logging in...
->
-> I assume PHP/Gallery works in similar fashion to Quixote session
-> management: there is a PHPSESSID session ID cookie, which simply
-> identifies the session. This is all that is "stored" on the client
-> side, server side there is then data associated with the session,
-> namely whether the user has logged in, and what his username is. The
-> result is that it is probably not possible to solve this problem by
-> simply setting cookies, you would have to get into PHP's session
-> datastructures from Quixote, or into Quixote's from PHP. Hence the
-> speculation that I may need to move some of this session information
-> into a shared data area, like the DB, or filesystem.

Looking at Gallery's Web site, you may be right: it doesn't seem to
require a database, so you might have to get into the less structured
situation of figuring out if (and how) it retains session information
in the filesystem.  Bummer.

I maintain that this will be cleaner and sturdier than doing some sort
of redirect trickiness, but it may not be simpler.

--titus