From: Matt Clark <matt@ymogen.net>
To: Pierre-Frédéric Caillaud <lists@boutiquenumerique.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Restricting Postgres
Date: Thu, 04 Nov 2004 23:32:57 +0000
Message-ID: <418ABC29.8090601@ymogen.net> (raw)
In-Reply-To: <opsgyq6mj7cq72hf@musicbox>
References: <003301c4c29a$f052d910$8300a8c0@solent>
<opsgyi89iccq72hf@musicbox>
<418A98C0.9010107@ymogen.net>
<opsgyneoj4cq72hf@musicbox>
<418AAF12.8030307@ymogen.net>
<opsgyq6mj7cq72hf@musicbox>
>
> A note though : you'll have to turn off HTTP persistent
> connections in your server (not in your proxy) or youre back to
> square one.
>
I hadn't considered that. On the client side it would seem to be up to
the client whether to use a persistent connection or not. If it does,
then yeah, a request every 5 seconds would still just hold open a
server. One more reason to use a proxy I s'pose.
>>
>> It's clear that this discussion has moved way away from PG! Although
>> in the context of DB backed web apps I guess in remains a bit
>> on-topic...
>
>
> I find it very on-topic as
> - it's a way to help this guy solve his "pg problem" which was iin
> fact a design problem
> - it's the future of database driven web apps (no more reloading
> the whole page !)
>
> I think in the future there will be a good bit of presentation
> login in the client...
Not if Bruno has his way ;-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: matt@ymogen.net, lists@boutiquenumerique.com
Subject: Re: Restricting Postgres
In-Reply-To: <418ABC29.8090601@ymogen.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox