From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
---|---|
To: | William Yu <wyu(at)talisys(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: Application using PostgreSQL as a back end (experienced programmers |
Date: | 2005-11-16 21:12:05 |
Message-ID: | 20051116211205.GA24897@wolff.to |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Wed, Nov 16, 2005 at 08:02:52 -0800,
William Yu <wyu(at)talisys(dot)com> wrote:
>
> Of course, there's the idea of not bothering with AJAX and just living
> with the perceived delays. It ends up not being a big deal because (1)
> users expect such delays on the web and (2) users get used to such
> delays on the web. It was a bit of a concern when we developed our
> insurance app as 100% web-based -- users accustomed to switching to
> different pages of info instantaneously going to 1 second just for the
> browser/submit/return latency. But it ended up being not an issue. Users
Option 2 also works for people who don't enable javascript.
I have to really need to use a site before I will enable javascript to use
the site instead of walking away. Even in that case I will often examine the
javascript code to see if I can bypass it without having to enable to get
things done. (As an aside, doing this I have found some sites that only
validate data on the client and not on the server.)
From | Date | Subject | |
---|---|---|---|
Next Message | Obe, Regina DND\MIS | 2005-11-16 22:11:19 | Re: Application using PostgreSQL as a back end (experien |
Previous Message | Flávio Brito | 2005-11-16 20:41:36 | Receive a record not a tuple - plpgsql |