Re: Restricting Postgres - Mailing list pgsql-performance

From Matt Clark
Subject Re: Restricting Postgres
Date
Msg-id 418AAF12.8030307@ymogen.net
Whole thread Raw
In response to Re: Restricting Postgres  (Pierre-Frédéric Caillaud<lists@boutiquenumerique.com>)
Responses Re: Restricting Postgres  (Bruno Wolff III <bruno@wolff.to>)
Re: Restricting Postgres  (Pierre-Frédéric Caillaud<lists@boutiquenumerique.com>)
List pgsql-performance
>
>     In your webpage include an iframe with a Javascript to refresh it
> every  five seconds. The iframe fetches a page from the server which
> brings in  the new data in form of generated JavaScript which writes
> in the parent  window. Thus, you get a very short request every 5
> seconds to fetch new  data, and it is displayed in the client's window
> very naturally.
>
> ...

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.

http://developer.apple.com/internet/webcontent/xmlhttpreq.html is a good
starting point.

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...

M

pgsql-performance by date:

Previous
From: T E Schmitz
Date:
Subject: appropriate indexing
Next
From: Matt Clark
Date:
Subject: Re: appropriate indexing