On Sep 11, 2007, at 7:51 AM, hollowsun@waitrose.com wrote:

> In a previous mail Mario wrote (about sessions): "You are not
> obliged to use Durus. Any other persistence mechanism will do, as
> long as you satisfy the API as defined in the class
> qp.pub.publisher.DurusPublisher." I was wondering if anyone had
> already done the work and plugged QP into MySQL or even better
> PostgresSQL? I have nothing against Durus, in fact like it, but my
> hosting provider already provides MySQL and Postgres instances for
> me to use and will charge extra for using Durus because it will
> count as another chargeable "long running process" along with QP
> itself. An increase in cost I'd like to avoid. Regards, Tristan

Another possible option would be to run qp with only one process, and
have that process
connect directly to the durus file using a FileStorage instead of a
ClientStorage.