From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | Matt Clark <matt(at)ymogen(dot)net> |
Cc: | Pierre-Frédéric Caillaud <lists(at)boutiquenumerique(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Restricting Postgres |
Date: | 2004-11-04 23:14:29 |
Message-ID: | 20041104231429.GA15541@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-performance |
On Thu, Nov 04, 2004 at 22:37:06 +0000,
Matt Clark <matt(at)ymogen(dot)net> wrote:
> >...
>
> Yup. If you go the JS route then you can do even better by using JS to
> load data into JS objects in the background and manipulate the page
> content directly, no need for even an Iframe. Ignore the dullards who
> have JS turned off - it's essential for modern web apps, and refusing JS
> conflicts absolutely with proper semantic markup.
Javascript is too powerful to turn for any random web page. It is only
essential for web pages because people write their web pages to only
work with javascript.
From | Date | Subject | |
---|---|---|---|
Next Message | Pierre-Frédéric Caillaud | 2004-11-04 23:21:48 | Re: Restricting Postgres |
Previous Message | Alvaro Herrera | 2004-11-04 22:44:53 | Re: how to edit a function from psql? |
From | Date | Subject | |
---|---|---|---|
Next Message | Pierre-Frédéric Caillaud | 2004-11-04 23:21:48 | Re: Restricting Postgres |
Previous Message | Matt Clark | 2004-11-04 23:08:59 | Re: Better Hardware, worst Results |